Monitoring system with bridges for interconnecting system elements

ABSTRACT

Systems, methods, and devices for monitoring operation of industrial equipment are disclosed. In one embodiment, a monitoring system is provided that includes a passive backplane and one more functional circuits that can couple to the backplane. Each of the functional circuits that are coupled to the backplane can have access to all data that is delivered to the backplane. Therefore, resources (e.g., computing power, or other functionality) from each functional circuits can be shared by all active functional circuits that are coupled to the backplane. Because resources from each of the functional circuits can be shared, and because the functional circuits can be detachably coupled to the backplane, performance of the monitoring systems can be tailored to specific applications. For example, processing power can be increased by coupling additional processing circuits to the backplane.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/181,255, filed Feb. 22, 2021, entitled, “MONITORING SYSTEM WITHBRIDGES FOR INTERCONNECTING SYSTEM ELEMENTS,” which is a continuation ofU.S. patent application Ser. No. 15/947,726, filed Apr. 6, 2018,entitled “MONITORING SYSTEM WITH BRIDGES FOR INTERCONNECTING SYSTEMELEMENTS,” each of which is incorporated herein by reference in itsentirety.

BACKGROUND

Many industries, such as hydrocarbon refining and power generation, canrely heavily upon operation of machinery, and in some instances,continuous operation of machinery. In these environments, failure of oneor more machines can incur significant costs due to repair expenses aswell as loss of production and potential injury to workers. Given theserisks, it can be common to monitor certain operating parameters of oneor more machine components. Measurements of the operating parameters canprovide an indication of the mechanical condition of a machinecomponent, allowing preventative maintenance (e.g., repair, replacement,etc.) to be performed on the machine component prior to failure. Thismonitoring can provide one or more long term benefits, such as lowerproduction costs, reduced equipment down time, improved reliability, andenhanced safety.

SUMMARY

Systems, devices, and methods for monitoring operating conditions ofmachines are provided. In one embodiments, a monitoring system isprovided that includes a bus having a plurality of coupling elements inelectronic communication with at least one data lane. The monitoringsystem can also include at least one slave circuit that can bedetachably coupled to at least one of the plurality of couplingelements. The at least one slave circuit can be configured to deliverdata to the at least one data lane. The slave circuit can have at leastone first gate configured to enable electronic communication between theslave circuit and the at least one data lane. The at least one firstgate can be configured to operate in a first operating mode and in asecond operating mode. The at least one first gate can configured toallow data to be transferred from the slave circuit to the at least onedata lane when in the first operating mode, and the at least one firstgate can be configured to prevent data from being transferred from theslave circuit to the at least one data lane when in the second operatingmode. The monitoring system can also include a master circuit that canbe detachably coupled to at least one of the plurality of couplingelements. The master circuit can be configured to deliver data to the atleast one data lane. The master circuit can have a first schedulecontroller configured to generate a first schedule and deliver datacharacterizing the first schedule to the at least one data lane. Thefirst schedule can specify when the at least one first gate is in thefirst operating mode and when the at least one first gate is in thesecond operating mode.

The monitoring system can vary in a number of ways. One or more of thefollowing features can be included in any feasible combination. Forexample, in one embodiments, the at least one slave circuit can includeat least one first gate controller in electronic communication with theat least one first gate. The at least one first gate controller can beconfigured to receive data characterizing the first schedule and tocontrol operation of the at least one first gate based on the data thatcharacterizes the first schedule.

In some embodiments, the at least one slave circuit can include a secondschedule controller that can be configured assume arbitrationresponsibilities, thereby enabling the second schedule controller togenerate a second schedule that defines when the at least one first gateis in the first operating mode and when the at least one first gate isin the second operating mode.

In some embodiments, the master circuit can include at least one secondgate that can be configured to enable electronic communication betweenthe master circuit and the at least one data lane. The at least onesecond gate can be configured to operate in a third operating mode andin a fourth operating mode. The at least one second gate can beconfigured to allow data to be transferred from the master circuit tothe at least one data lane when in the third operating mode, and the atleast one second gate can be configured to prevent data from beingtransferred from the master circuit to the at least one data lane whenin the fourth operating mode. The master circuit can also include atleast one second gate controller in electronic communication with thefirst schedule controller and the at least one second gate. The at leastone second gate controller can be configured to receive data thatcharacterizes the first schedule, and to control operation of the atleast one second gate based on the first schedule.

In some embodiments, the at least one slave circuit can include aplurality of slave circuits. Each slave circuit of the plurality ofslave circuits can be configured to receive data from the at least onedata lane of the bus.

In some embodiments, the monitoring system can include a sensor that canbe electrically coupled to the at least one slave circuit. The sensorcan be configured to measure operating parameters of a machine and todeliver data characterizing the measured operating parameters the atleast one slave circuit.

In some embodiments, the monitoring system can include a sensor inelectronic communication with the master circuit. The sensor can beconfigured to measure operating parameters of a machine and to deliveran analog sensor signal to the master circuit. The analog sensor signalcan characterizing the measured operating parameters of the machine.

In some embodiments, the slave circuit can be configured to receive adiscrete signal from at least one sensor measuring operating parametersof a machine, generate a digital signal based on the discrete signal,and deliver the digital signal to the at least one data lane.

In some embodiments, the master circuit can include an analog to digitalconverter configured to receive the analog sensor signal and convert theanalog sensor signal to a digital sensor signal.

In some embodiments, the at least one data lane can include a pluralityof parallel data lanes.

In some embodiments, the at least first one gate can include a 16 lanebidirectional differential transceiver.

In some embodiments, the at least one second gate can include a 16 lanebidirectional differential transceiver.

In some embodiments, the at least one data lane can include 16 datalanes. Each of the 16 data lanes can be a low voltage signaling pair.

In another aspect, a method is provided that includes generating a firstschedule for a first frame that includes at least one first time sliced.The first schedule can identify the at least one first time slice and atleast one slave circuit to which the at least one first time slice isassigned. The at least one slave circuit can be configured to provide adata packet to a bus of a monitoring system during the at least onefirst time slice. The method can also include generating a first beaconpacket that includes the first schedule, delivering the first beaconpacket to the bus of the monitoring system, and receiving the firstbeacon packet at the at least one slave circuit. The method can alsoinclude generating a first set of instructions for controlling operationof at least one gate of the at least one slave circuit based on the atleast one first time slice that is assigned to the at least one slavecircuit. The at least one gate can be configured to operate in a firstoperating mode and in a second operating mode. The at least one gate canbe configured to allow data to be transferred from the at least oneslave circuit to the bus when in the first operating mode, and the atleast one gate can be configured to prevent data from being transferredfrom the at least one slave circuit to the bus when in the secondoperating mode. The method can also include providing the first set ofinstructions to a gate controller of the at least one slave circuit,thereby configuring the gate controller to operate the at least one gatein the first operating mode during the at least one first time slice.

The method can vary in a number of ways. One or more of the followingfeatures can be included in any feasible combination. For example, insome embodiments, the first schedule can be generated by a schedulecontroller of a master circuit that is coupled to the bus.

In some embodiments, the method can include providing a data packet fromthe at least one slave circuit to the bus during the at least one firsttime slice.

In some embodiments, the method can also include determining that the atleast one slave circuit failed to provide a data packet to the busduring the at least one first time slice.

In some embodiments, the method can also include generating a beaconresponse packet based on the first schedule received with the firstbeacon packet. The beacon response packet can include a request for atleast one second time slice to be assigned to the at least one slavecircuit during a second frame. The method can also include deliveringthe beacon response packet to the bus of the monitoring system, andreceiving the beacon response packet at a master circuit, the mastercircuit being configured to generate a second schedule for the secondframe.

In some embodiments, the method can include generating the secondschedule for the second frame based on the beacon response packet. Thesecond frame can include the at least one second time slice. The secondschedule can identify the at least one second time slice and the atleast one slave circuit to which the at least one second time slice isassigned.

In some embodiments, the method can include generating a second beaconpacket that includes the second schedule. The method can also includedelivering the second beacon packet to the bus of the monitoring system,receiving the second beacon packet from the bus of the monitoringsystem, and generating a second set of instructions for controllingoperation of the at least one gate of the slave circuit based on the atleast one second time slice that is assigned to the slave circuit.

In some embodiments, the method can include delivering the second set ofinstructions to the gate controller of the slave circuit, therebyconfiguring the gate controller to operate the at least one gate in thefirst operating mode during the at least one second time slice.

In one embodiment, a system can include a bus and a master circuitdetachably coupled to the bus. The master circuit can include a managerbus node configured to interface with a first data lane of the bus. Thesystem can also include a plurality of slave circuits detachably coupledto the bus. A first slave circuit of the plurality of slave circuits caninclude a first slave bus node configured to interface with the firstdata lane. The master circuit can be configured to broadcast a firstbeacon packet during a first time slice of a first plurality of timeslices to the bus. The first beacon packet can include a first systemframe schedule indicative of an assignment of the first plurality oftime slices of a first system frame to one or more of the plurality ofslave circuits. The first plurality of time slices can be temporallyarranged relative to a first system frame reference time. The mastercircuit can also be configured to receive one or more beacon responsepackets from one or more of the plurality of slave circuits during asecond time slice of the first plurality of time slices. The first timeslice can be temporally adjacent to the first system frame referencetime and the second time slice can be temporally adjacent to the firsttime slice.

In one embodiment, the first slave circuit can be configured to receivethe first beacon packet and configure the first slave bus node totransmit data packets to the first data lane during a third time sliceof the first plurality of time slices. The first system frame schedulecan be indicative of assignment of the third time slice to the firstslave circuit.

In one embodiment, the master circuit can be further configured todetermine a set of valid beacon response packets from the one or morebeacon response packets received during the second time slice. Themaster circuit can also be configured to generate a second beacon packetincluding a second system frame schedule indicative of assignment of asecond plurality of time slices of a second system frame to one or moreof the plurality of slave circuits. Assignment of the second pluralityof time slices can be based on time slice requests in the set of validbeacon response packets.

In one embodiment, the determination of the set of valid beacon responsepackets can be based on transmission collisions of the one or morebeacon response packet in the first data lane of the bus. In anotherembodiment, the second plurality of time slices can be temporallyarranged relative to a second system frame reference time. In yetanother embodiment, the first slave bus node can include a first nodecontroller, a first gate controller and a first plurality of gates. Thefirst gate controller can configure one or more gates of the firstplurality of gates to transmit data packets from the first nodecontroller to the first data lane.

In one embodiment, the master circuit can assign of a fourth time sliceof the second plurality of time slices to a second slave circuit of theplurality of slave circuits based on a unique identification of thesecond slave circuit in a second beacon response packet broadcasted onthe first data lane by the second slave circuit. In another embodiment,the master circuit can be further configured to cancel the assignment ofthe fourth time slice to the second slave circuit based on inactivity ofthe second slave circuit during one or more time slices assigned to thesecond slave circuit.

In one embodiment, the second beacon packet can be generated at anapplication layer executed in a slave circuit controller in the secondslave circuit. In another embodiment, the second slave circuit caninclude a second slave circuit clock, and the second slave circuit canbe configured to synchronize the second slave circuit clock based on oneor both of the first system frame reference time and the second systemframe reference time. In another embodiment, the first slave bus nodecan be further configured to maintain a copy of the first beacon packet.In yet another embodiment, the first time slice can include a dead bandand a usable time slice period.

In one embodiment, the master circuit can be configured to broadcast thefirst beacon packet during the usable time slice period, and configuredto prevent broadcast of the first data packet during the dead band. Inanother embodiment, the first plurality of time slices can include oneor both of an unassigned time slice and a best-effort time slice. Themaster circuit can be configured to discard data packets broadcasted byone or more slave circuits of the plurality of slave circuits during theunassigned time. The one or more slave circuits of the plurality ofslave circuits can broadcast an asynchronous application layer eventduring the best-effort time slice.

In one embodiment, a method can include broadcasting a first beaconpacket during a first time slice of a first plurality of time of a firstsystem frame slices to a first data lane of a bus. The first beaconpacket can include a first system frame schedule indicative ofassignment of the first plurality of time slices to one or more of aplurality of slave circuits coupled to the bus. The first plurality oftime slices can be temporally arranged relative to a first system framereference time. The method can also include receiving one or more beaconresponse packets from one or more of the plurality of slave circuitsduring a second time slice of the first plurality of time slices. Thefirst time slice can be temporally adjacent to the first system framereference time and the second time slice can be temporally adjacent tothe first time slice. The method can further include generating a secondbeacon packet including a second system frame schedule indicative ofassignment of a second plurality of time slices of a second system frameto one or more of the plurality of slave circuits. The method can alsoinclude providing the second beacon packet to the one or more of theplurality of slave circuits. The broadcasting, the receiving, thegenerating and the providing can be by a master circuit detachablycoupled to the bus, the master circuit can include a manager bus nodeconfigured to interface with the first data lane of the bus.

In one embodiment, the method can further include determining a set ofvalid beacon response packets from the one or more beacon responsepackets received during the second time slice. Assignment of the secondplurality of time slices can be based on time slice requests in the setof valid beacon response packets. In another embodiment, determinationof the set of valid beacon response packets can be based on transmissioncollisions of the one or more beacon response packet in the first datalane of the bus. In yet another embodiment, the second plurality of timeslices can be temporally arranged relative to a second system framereference time.

In one embodiment, the method can further include receiving the firstbeacon packet by a first slave circuit of the plurality of slavecircuits. The first slave circuit can include a first slave bus nodeconfigured to interface with the first data lane. The method can alsoinclude configuring the first slave bus node to transmit data packets tothe first data lane during a third time slice of the first plurality oftime slices. The first system frame schedule can include assignment ofthe third time slice can be to the first slave circuit. In anotherembodiment, the method can further include the first slave bus node caninclude a first node controller, a first gate controller and a firstplurality of gates. In yet another embodiment, configuring the firstslave bus node to transmit data packets can include configuring one ormore gates of the first plurality of gates, by the first gatecontroller, to transmit the data packets from the node controller to thefirst data lane.

In one embodiment, the method can further include assignment of a fourthtime slice of the second plurality of time slices to a second slavecircuit of the plurality of slave circuits based on a uniqueidentification of the second slave in a beacon response packet receivedfrom the second slave circuit. In one embodiment, the method can furtherinclude cancelling the assignment of the fourth time slice to the secondslave circuit based on inactivity of the second slave circuit during oneor more time slices assigned to the second slave circuit.

In one embodiment, a monitoring system can include a first backplanehaving at least one first data lane. The monitoring system can alsoinclude at least one second data lane in parallel with the at least onefirst data lane. The monitoring system can also include at least onefirst port in electronic communication with the at least one first datalane and the at least one second data lane. The monitoring system canalso include at least one second port in electronic communication withthe at least one first data lane and the at least one second data lane.The monitoring system can further include a first functional circuitdetachably coupled to the at least one first port. The first functionalcircuit can be configured to receive a sensor signal from a sensor. Thesensor signal can characterize measured operating parameter of amachine. The functional circuit can be configured to generate a firstdigital signal based on the sensor signal, and deliver the first digitalsignal to the at least one first data lane. The monitoring system canalso include a second functional circuit detachably coupled to the atleast one second port. The second functional circuit can be configuredto receive the first digital signal from the at least one first datalane. The second functional circuit can also be configured to determinean operating status of the machine based on the received first digitalsignal and a predetermined operating threshold. The second functionalcircuit can further be configured to generate a second digital signalbased on the first digital signal and the predetermined operatingthreshold. The second digital signal characterizing the operating statusof the machine, and deliver the second digital signal to the at leastone second data lane.

In one embodiment, the monitoring system can include at least one thirddata lane in parallel with the at least one first data lane and the atleast one second data lane. The monitoring system can also include atleast one third port in electronic communication with the at least onefirst data lane, the at least one second data lane, and the at least onethird data lane. The monitoring system can also include a thirdfunctional circuit detachably coupled to the at least one third port.The third functional circuit can be configured to receive the seconddigital signal from the at least one second data lane, and actuate arelay based the operating status of the machine.

In one embodiment, the first functional circuit not in electroniccommunication with the at least one second data lane. In anotherembodiment, the at least one first data lane can be a dedicated datalane and can be configured to receive data from only the firstfunctional circuit. In yet another embodiment, the second functionalcircuit may not be in electronic communication with the at least onefirst data lane.

In one embodiment, the at least one second data lane can be a dedicateddata lane and can be configured to receive data from only the secondfunctional circuit. In another embodiment, the first functional circuitcan include a first unidirectional gate configured to allow the firstfunctional circuit to deliver the first digital signal to the at leastone first data lane. In yet another embodiment, the first functionalcircuit can include a gate pair which can include a transmitter and areceiver. The transmitter can be configured to deliver a third digitalsignal from the at least one third data lane, and the receiver can beconfigured to receive a fourth digital signal from the at least onethird data lane.

In one embodiment, the second functional circuit can include a gate paircomprising a transmitter and a receiver, the transmitter can beconfigured to deliver a third digital signal to the at least one thirddata lane, and the receiver can be configured to receive a fourthdigital signal from the at least one third data lane. In anotherembodiment, the second functional circuit can include a secondunidirectional gate configured to allow the second functional circuit toreceive the first digital signal from the at least one first data lane.In yet another embodiment, the at least one third data lane can be abi-directional serial data lane.

In one embodiment, the at least one first data lane can be aunidirectional serial data lane. In another embodiment, the at least onesecond data lane can be a unidirectional serial data lane. In yetanother embodiment, the at least one first data lane comprises aplurality of first data lanes.

In one embodiment, the at least one second data lane comprises aplurality of second data lanes. In another embodiment, the at least onefirst port can be electrically decoupled from the at least one seconddata lane, thereby preventing electronic communication between the firstfunctional circuit and the at least one second data lane. In yet anotherembodiment, the monitoring system can further include at least onefourth port in electronic communication with the at least one third datalane and a fourth functional circuit coupled to the at least one fourthport. The fourth functional circuit can be configured to deliver a thirddigital signal to the second functional circuit via the at least onethird data lane. The third signal can characterize updated operatingthresholds.

In one embodiment, the at least one fourth port can be electricallydecoupled from the at least one first data lane, thereby preventingelectronic communication between the fourth functional circuit and theat least one first data lane. In another embodiment, the fourthfunctional circuit can include a schedule controller configured togenerate a first schedule.

In one embodiment, a method, can include delivering, from a firstfunctional circuit of a monitoring system, a first digital signal to afirst data lane of a backplane of a monitoring system. The first digitalsignal can characterize a measured operating parameter of a machine. Themethod, can include receiving the first digital signal from the firstdata lane, at a second functional circuit of the monitoring system. Themethod, can also include determining an operating status of the machinebased on the received first digital signal and a predetermined operatingthreshold. The method, can further include generating a second digitalsignal based on the first digital signal and the predetermined operatingthreshold, the second digital signal characterizing the operating statusof the machine. The method can also include delivering the seconddigital signal to a second data lane of the backplane, receiving thesecond digital signal from the second data lane at a third functionalcircuit, and actuating a relay based the operating status of themachine.

In one embodiment, the method can include receiving, at the firstfunctional circuit, an analog signal from a sensor, the analog signalcharacterizing the measured operating parameter of the machine. Themethod can also include converting the analog signal to the firstdigital signal. In another embodiment, the method can include generatinga third digital signal characterizing updated operating thresholds, anddelivering the third digital signal to a third data lane of thebackplane. The third signal can characterize updated operatingthresholds.

In one embodiment, the analog signal can be converted to the firstdigital signal at a fixed rate. In another embodiment, the method canfurther include filtering the analog signal. In yet another embodiment,the method can further include delivering a signal to a control systemupon actuation of the relay to stop operation of the machine.

Systems, devices, and methods for monitoring operating conditions ofmachines are provided. In one embodiment, a monitoring system isprovided that includes a first backplane having a first set of datalanes and a first set of ports. Each port of the first set of ports canbe in electronic communication with at least one data lane of the firstset of data lanes. The monitoring system can include a second backplanehaving a second set of data lanes and a second set of ports. Each of thesecond set of ports can be in electronic communication with at least onedata lane of the second set of data lanes. The monitoring system canfurther include a first bridge circuit that can be detachably coupled toat least one of the first set of ports, and a second bridge circuitdetachably coupled to at least one of the second set of ports. Thesecond bridge circuit can be in electronic communication with the firstbridge circuit. The first bridge circuit can be configured to receive afirst set of data from the first set of data lanes, convert the firstset of data to a first serial data stream, and to deliver the firstserial data stream to the second bridge circuit, thereby delivering thefirst set of data to the second backplane. The second bridge circuit canbe configured to receive a second set of data from the second set ofdata lanes, convert the second set of data to a second serial datastream, and to deliver the second serial data stream to the first bridgecircuit, thereby delivering the second set of data to the firstbackplane.

The monitoring system can vary in a number of ways. One or more of thefollowing features can be included in any feasible combination. Forexample, in some embodiments, the first bridge circuit can include atleast one first gate configured to facilitate electronic communicationbetween the first bridge circuit and at least one data lane of the firstset of data lanes. The at least one first gate can be configured tooperate in a first operating mode and in a second operating mode. The atleast one first gate can be configured to allow data to be transferredfrom the first bridge circuit to the at least one data lane of the firstset of data lanes when in the first operating mode. The at least onefirst gate can be configured to prevent data from being transferred fromthe first bridge circuit to the at least one data lane of the first setof data lanes when in the second operating mode. The monitoring systemcan also include at least one first gate controller in electroniccommunication with the at least one first gate. The at least one firstgate controller can be configured control operation of the at least onefirst gate.

In some embodiments, the second bridge circuit includes the secondbridge circuit can include at least one second gate configured tofacilitate electronic communication between the second bridge circuitand at least one data lane of the second set of data lanes. The at leastone second gate can be configured to operate in a third operating modeand a fourth operating mode. The at least one second gate can beconfigured to allow data to be transferred from the second bridgecircuit to the at least one lane of the second set of data lanes when inthe third operating mode. The at least one second gate can be configuredto prevent data from being transferred from the second bridge circuit tothe at least one lane of the second set of data lanes when in the fourthoperating mode. The second bridge circuit can also include at least onesecond gate controller in electronic communication with the at least onesecond gate and the at least one first gate controller. The at least onesecond gate controller can be configured control operation of the atleast one second gate.

In some embodiments, the monitoring system can also include a first setof functional circuits. Each functional circuit of the first set offunctional circuits can be detachably coupled to at least one port ofthe first set of ports. The first set of functional circuits can beconfigured to deliver the first set of data to the first backplane andto selectively receive any data delivered to the first backplane. Themonitoring system can also include a second set of functional circuits.Each functional circuit of the second set of functional circuits can bedetachably coupled to at least one port of the second set of ports. Thesecond set of functional circuits can be configured to deliver a secondset of data to the second backplane and to selectively receive any datadelivered to the second backplane.

In some embodiments, the first set of functional circuits can include atleast one first functional circuit. The first functional circuit caninclude at least one second gate configured to facilitate electroniccommunication between the at least one first functional circuit and atleast one of the first set of data lanes. The at least second one gatebeing configured to operate in a first operating mode and a secondoperating mode. The at least one second gate can be configured to allowdata to be transferred from the at least one first functional circuit tothe at least one lane of the first set of data lanes when in the firstoperating mode. The at least one second gate can be configured toprevent data from being transferred from the at least one firstfunctional circuit to the at least one lane of the first set of datalanes when in the second operating mode.

In some embodiments, the first set of data lanes can include a pluralityof data lanes.

In some embodiments, the second set of data lanes can include aplurality of data lanes.

In some embodiments, the monitoring sensor can include a sensor inelectronic communication with a functional circuit of at least one ofthe first set of functional circuits and the second set of functionalcircuits. The sensor can be configured to measure operating parametersof a machine and to deliver data characterizing the measured operatingparameters to the functional circuit.

In some embodiments the first set of functional circuits can include aplurality of functional circuits. Each functional circuit of theplurality of functional circuits can be configured to receive data fromat least one data lane of the first set of data lanes.

In some embodiments, the first backplane and the second backplane can bepassive backplanes that not include active switches.

In another aspect, a method is provided that includes receiving a firstidentification data at a first bridge circuit coupled to a firstbackplane of a first monitoring subsystem. The first identification datacan characterize information identifying hardware of a second monitoringsubsystem. The method can also include receiving a second identificationdata at a second bridge circuit coupled to a second backplane of thesecond monitoring subsystem. The second identification data cancharacterize information identifying hardware of the first monitoringsubsystem. The method can further include determining, using the firstidentification data and the second identification data, that firstmonitoring subsystem is compatible with the second monitoring subsystem.The method can also include receiving a first schedule at the secondbridge circuit. The first schedule can characterize a firstcommunication schedule for a first set of functional circuits that arein electronic communication with the first backplane. The method canfurther include receiving a second schedule at the first bridge circuit.The second schedule can characterize a second communication schedule fora second set of functional circuits that are in electronic communicationwith the second backplane. The method can further include comparing thefirst communication schedule to the second communication schedule anddetermining that the first schedule is compatible with the secondschedule. The method can further include providing a first signal to atleast one first gate of the first bridge circuit and providing a secondsignal to at least one second gate of the second bridge circuit, therebyactivating the at least one first gate and the at least one second gate,and facilitating electronic communication between the first backplaneand the second backplane.

The method can vary in a number of ways. One or more of the followingfeatures can be included in any feasible combination. For example, themethod can include delivering, from the first set of functionalcircuits, a first set of parallel data streams to a first set ofparallel data lanes of the first backplane. The method can also includereceiving, at the first bridge circuit, the first set of parallel datastreams from the first set of parallel data lanes of the firstbackplane, converting the first set of parallel data streams to a firstserial data stream, and delivering the first serial data stream to thesecond bridge circuit. The method can further include expanding thefirst serial data stream to a second set of parallel data streams, anddelivering the second set of parallel data streams to a second set ofparallel data lanes.

In some embodiments, the method can include amplifying a power of thefirst serial data stream based on a distance between the first bridgecircuit and the second bridge circuit.

In some embodiments, the method can include delivering, from the secondset of functional circuits, a third set of parallel data streams to thesecond set of parallel data lanes of the second backplane.

In some embodiments, the method can include receiving, at the secondbridge circuit, the third set of parallel data streams from the secondset of parallel data lanes of the second backplane, converting the thirdset of parallel data streams to a second serial data stream, anddelivering the second serial data stream to the first bridge circuit.The method can also include expanding the second serial data stream to afourth set of parallel data streams, and delivering the fourth set ofparallel data streams to the first set of parallel data lanes.

In some embodiments, the method can include generating a third scheduleusing at least one functional circuit of the first set of functionalcircuits. The third schedule can include data that determines when eachfunctional circuit of the first set of functional circuits delivers datato the first set of parallel data lanes and when each functional circuitthe second set of functional circuits delivers data to the second set ofparallel data lanes.

In some embodiments, the third set of parallel data streams can includesensor data characterizing measured operating values of a machine. Thesensor data can be measured by sensors coupled to the machine.

In some embodiments, the method can include amplifying a power of thesecond serial data stream based on a distance between the first bridgecircuit and the second bridge circuit.

In some embodiments, the method can include determining an estimateddelay time that can characterize an estimated amount of time required totransfer data between the first bridge circuit and the second bridgecircuit. The method can also include determining a dead band periodbased on at least one of the first communication schedule and the secondcommunication schedule. The dead band time can characterize a totalamount of time available to absorb delays in communication between oneor more backplane. The method can further include determining an amountof the dead band time that is available based on at least one of thefirst communication schedule and the second communication schedule, andcomparing the estimated delay time to the amount of dead band time thatis available.

In some embodiments, the method can include receiving a first networkidentification data at the first bridge circuit. The first networkidentification data can characterize a first network configuration. Themethod can also include receiving a second network identification dataat the second bridge circuit. The second network identification data cancharacterize a second network configuration. The method can furtherinclude comparing the first network identification data with the secondnetwork identification data.

DESCRIPTION OF DRAWINGS

These and other features will be more readily understood from thefollowing detailed description taken in conjunction with theaccompanying drawings, in which:

FIG. 1A is a block diagram illustrating one exemplary embodiment of anoperating environment containing an existing monitoring system;

FIG. 1B is a block diagram illustrating one exemplary embodiment of abackplane of the monitoring system of FIG. 1A;

FIG. 2 is a block diagram illustrating one exemplary embodiment of anoperating environment containing a flexible monitoring system configuredto monitor a machine;

FIG. 3 is a diagram illustrating families of various types of functionalcircuits that can be used with the scalable monitoring system shown inFIG. 2 ;

FIG. 4 is block diagram of a portion of an exemplary embodiment of amonitoring system;

FIG. 5 is a block diagram of an exemplary embodiment of a functionalcircuit that includes two nodes;

FIG. 6 is block diagram of an exemplary embodiment of a functionalcircuit that does not include transmitters;

FIG. 7 is a diagram illustrating components of system frames;

FIG. 8 is an exemplary data structure of a beacon packet;

FIG. 9 is an exemplary structure of system frame schedule;

FIG. 10 is an exemplary data structure of a beacon response packet;

FIG. 11 is an exemplary communication protocol between a master circuitand a slave circuit;

FIG. 12 is an exemplary structure of a data packet that can be deliveredto the backplane of a monitoring system during operation;

FIG. 13 is flow diagram that illustrates an exemplary initializationprocess;

FIG. 14 is flow diagram that illustrates an exemplary method ofgenerating a schedule based on the communication requests from slavecircuits;

FIG. 15 is a flow diagram illustrating an exemplary method of processingtime slice requests from beacon response packets and generating aschedule entry array;

FIG. 16 is a flow diagram of an exemplary traffic monitoring processthat can be used to recover unused time slices;

FIG. 17 is shown an exemplary of a schedule entry array that includes atime slice array, an assignment array, a length array, and a counterarray;

FIG. 18 is a flow diagram illustrating exemplary operation of a node ofa slave circuit of a monitoring system;

FIG. 19 is a block diagram of an exemplary embodiment of a bridgecircuit that can be configured to facilitate electronic communicationbetween backplanes of a monitoring system;

FIG. 20 is a block diagram of an exemplary embodiment of a monitoringsystem that includes two monitoring subsystems that are coupled usingbridge circuits;

FIG. 21 is a magnified view of the block diagram of the monitoringsystem shown in FIG. 20 ;

FIG. 22 is a data flow diagram illustrating exemplary communicationbetween various components of the monitoring system illustrated in FIG.20 ;

FIG. 23 is a flow chart illustrating an exemplary method of determiningcompatibility of backplanes;

FIG. 24 is a block diagram of another exemplary monitoring system thatincludes two monitoring subsystems that are coupled using bridgecircuits;

FIG. 25 is block diagram of another exemplary monitoring system thatincludes two monitoring subsystems that are coupled using bridgecircuit;

FIG. 26 is a block diagram of an exemplary monitoring system thatutilizes a time-sensitive networking (TSN) Ethernet protocol tofacilitate communication between functional circuits of the monitoringsystem;

FIG. 27 is a detailed view of a portion of the monitoring system shownin FIG. 27 ;

FIG. 28 is block diagram of another exemplary monitoring system thatutilizes TSN Ethernet protocol to facilitate communication betweenfunctional circuits of the monitoring system;

FIG. 29 is a block diagram of a portion of an exemplary embodiment of amonitoring system utilizes dedicated data lanes to facilitatecommunication between functional circuits;

FIG. 30 is a magnified view input circuits of the monitoring systemshown in FIG. 30 ;

FIG. 31 is a magnified view of a system interface circuit of themonitoring system shown in FIG. 29 ;

FIG. 32 is a magnified view of protection circuit of the monitoringsystem shown in FIG. 29 ;

FIG. 33 is a magnified view of relay circuits of the monitoring systemshown in FIG. 30 ;

FIG. 34 shows a magnified view of the gateway circuit of the monitoringsystem shown in FIG. 29 ;

FIG. 35 is a magnified view of a 4-20 output circuit of the monitoringsystem shown in FIG. 29 ;

FIG. 36 is a block diagram of an exemplary backplane of the monitoringsystem shown in FIG. 29 ;

FIG. 37 is a data flow diagram illustrating exemplary communicationbetween various components of the monitoring system shown in FIG. 29 ;

FIG. 38 is a block diagram another exemplary embodiment of a monitoringsystem that utilizes dedicated data lanes;

FIG. 39 shows a magnified view of input circuits and a system interfacecircuit of the monitoring system shown in FIG. 38 ;

FIG. 40 is a magnified view of protection circuits of the monitoringsystem shown in FIG. 38 ;

FIG. 41 is a magnified view of a relay circuit, a 4-20 output circuit,and a condition monitoring circuit of the monitoring system shown inFIG. 38 ; and

FIG. 42 is a block diagram of an exemplary backplane of the monitoringsystem shown in FIG. 38 .

DETAILED DESCRIPTION

Certain exemplary embodiments will now be described to provide anoverall understanding of the principles of the structure, function,manufacture, and use of the systems, devices, and methods disclosedherein. One or more examples of these embodiments are illustrated in theaccompanying drawings.

Industrial monitoring systems, such as wind turbines, can be used tomonitor operating conditions of industrial systems. Although industrialmonitoring systems can provide users with useful information regardingoperation of industrial systems, some monitoring systems can be limitedin terms of flexibility and/or scalability. Additionally, costs andcomplexity of installation can create a significant barrier to entry forsome users that want to monitor low cost and/or low prioritycomponents/systems. Systems, methods, and devices are provided thatimprove flexibility and scalability of monitoring systems. In oneembodiment, a monitoring system is provided that includes a passivebackplane and one or more functional circuits that can couple to thebackplane. Each of the functional circuits has access to all data thatis delivered to the backplane. Therefore, resources (e.g., computingpower) from each functional circuit can be shared by all activefunctional circuit that are coupled to the backplane. Because resourcesfrom each functional circuit can be shared, and because the functionalcircuits can be detachably coupled to the backplane, performance of themonitoring systems adjusted and/or scaled to fit individual monitoringneeds. For example, processing power can be increased by couplingadditional processing circuits to the backplane. The shared data anddetachable functional circuits also allow for multiple backplanes to becoupled using bridges. Bridging can allow multiple backplanes to sharecommon resources, which can provide flexibility when designing andinstalling monitoring systems. For example, monitoring subsystems can beinstalled remotely near industrial equipment such that the functionalcircuits can receive sensor data, while other monitoring subsystems canbe installed at another location that may be more convenient, easier toaccess, or more cost effective.

Embodiments of systems and corresponding methods for monitoringindustrial machines are discussed herein. However, embodiments of thedisclosure can be employed with other machines without limit.

An operating environment 100 containing an existing monitoring system isillustrated in FIG. 1 . The operating environment 100 can include atarget 102, at least one sensor 104, and a monitoring system 106 incommunication with the sensor 104, an internal network 110 a, and anexternal network 110 b.

The target 102 can be any component of any machine. Examples of thetarget 102 can include gears, bearings, and shafts, amongst others.Examples of machines can include turbomachines, turbines (e.g., hydro,wind), generators, and reciprocating compressors.

The sensor 104 can be configured to sense an operating parameter of thetarget 102, to generate at least one sensor signal 104 s representingthe measured operating parameter, and to transmit the sensor signal 104s to the monitoring system 106 (e.g., via field wiring). As an example,the sensor 104 can include a probe, a transducer, and a signalconditioning circuit (not shown). The probe can interact with the target102 for measurement of the operating parameter. The transducer canconvert measurements of the operating parameter into an electricalsignal (e.g., a voltage). The signal conditioning circuit can conditionand/or amplify the electrical signal to generate the sensor signal 104 s(e.g., a voltage ranging between a minimum and maximum). Thus, in oneaspect, the sensor signal 104 s can contain the direct or rawmeasurement made by the sensor transducer. The sensor signal 104 s canbe an analog signal or a digital signal.

In another aspect, the sensor signals 104 s can also include an enhanceddata set, in addition to the direct measurements of the operatingparameter. The enhanced data set can contain a variety of measuredvariables that depend upon the type of operating parameter beingmeasured. As an example, the target 102 can be a rotating component,such as a shaft, and radial vibration can be a variable measured by asensor 104 in the form of a proximity sensor. Under these circumstances,the enhanced data set can include one or more of a gap voltage, a 1×filtered amplitude, a 2× filtered amplitude, a 1× filtered phase, a 2×filtered phase, Not 1× amplitude, and maximum shaft displacement (Smax).Gap voltage is the voltage output by the probe and represents thephysical distance between the target 102 and a tip of the probe. 1×amplitude is the amplitude of vibrations having the same frequency asthe shaft rotation, while 2× amplitude is the amplitude of vibrationshaving a frequency twice that of the shaft rotation. For instance, arotation speed of 1480 revolutions per minute corresponds to a frequencyof 24.66 cycles per second (Hz). Phase is the time delay between avibration measured at a predetermined measurement location with respectto a reference location. Thus, 1× phase refers to phase of vibrationshaving the same frequency as the shaft rotation, while 2× phase refersto phase of vibrations having a frequency twice that of the shaftrotation. Not 1× amplitude refers to all amplitudes except for the 1×amplitude. In other embodiments, the enhanced data set can includemetadata regarding one or more components of the sensor 104, such as thetransducer. Examples of metadata can include one or more of a serialnumber, revision number, operating temperature, and state of health.

The number and type of sensor 104 can be dictated by the operatingparameter(s) that are intended to be measured. In one aspect, the sensor104 can take the form of one or more proximity probes for measurement ofvibration, position, speed, direction of motion, and eccentricity. Inanother aspect, the sensor 104 can take the form of one or moreaccelerometers for measurement of seismic vibration and acceleration. Ina further aspect, the sensor 104 can take the form of one or moretemperature probes or pressure probes for measurement of temperature andpressure, respectively. It can be understood that the sensor types andcorresponding operating parameters listed above are not exhaustive andembodiments of the sensor 104 can include any sensor or combination ofsensors suitable for measurement of operating parameters of interest.

In use, the monitoring system 106 can be configured to process thereceived sensor signals 104 s and output monitoring signals 106 s, 108s. As an example, the monitoring system 106 can be configured todetermine a value characterizing an operating parameter measurement. Themonitoring system 106 can also compare this determined value, and/or anymeasured variables of the enhanced data set, to one or morecorresponding predetermined alarm conditions in real-time and determinean alarm status (e.g., OK, not OK, alert, danger, etc.). For instance,when the target 102 is a rotating shaft and the measured operatingparameter is radial vibration of the shaft, the sensor signal 104 s caninclude measurements of displacement of the shaft as a function of time.From the sensor signal 104 s, the monitoring system 106 can determinethe value of vibration amplitude from the peak-to-peak displacement.

The monitoring system 106 can also be configured to output monitoringsignals 106 s, 108 s to the internal network 110 a and/or the externalnetwork 110 b. The output monitoring signals 106 s, 108 s can includeone or more of the measured variables of the enhanced data set, thedetermined values, and the determined status. Alarm statuses, such asalert and danger, can be annunciated via physical relays on themonitoring system 106 or to the external systems 110 by the monitoringsignals 106 s, 108 s. In another aspect, the monitoring system 106 canadditionally or alternatively store the sensor signals 104 s for laterprocessing.

The internal network 110 a can be a plant network that is incommunication with a machine control system 112. The machine controlsystem 112 can be configured to provide commands to a machine operativeto control one or more operating parameters of the target 102. Theinternal network 110 a can also be in communication with other systems,such as computing devices executing configuration software (not shown),human-machine interfaces (HMIs) 114 and/or a customer historian 116. Theconfiguration software can be used to provide configuration information,such as the pre-determined alarm conditions, to the monitoring system106. The HMI 114 can be one or more computing devices in communicationwith user interface devices (e.g., displays) allowing an operator of themachine to review measured operating parameters and/or provideinstructions to the machine control system 112.

So configured, the monitoring system 106 can facilitate protection of amachine containing the target 102. As an example, in response toannunciation of an alarm status, the machine control system 112 can beutilized to control operation of the target 102 (e.g., automaticallyaccording to programmed logic or manually using the HMI 114) to causethe measured operating parameters to change and move out of the alarmstatus. Under extreme circumstances, the machine control system 112 canbe employed to shut down operation of the machine to protect the target102 from damage and/or workers from injury. The historian 116 can storeany of the data contained within the monitoring signals 106 s.

The external network 110 b can be a business network that is incommunication with a diagnostic system 120. The diagnostic system 120can analyze any of the data contained within the monitoring signals 108s received from the monitoring system 106 to diagnose improper operationof the target 102 and/or predict improper operation of the target 102before it occurs. Thus, by providing monitoring signals 108 s to theexternal network 110 b, the monitoring system 106 can facilitatecondition monitoring of the target 102.

The monitoring system 106 is illustrated in greater detail in FIG. 1B.As shown, the monitoring system 106 includes a backplane 150 that can beconfigured to allow communication between different components coupledthereto. The components can include a measurement processing circuit 152a, a relay output circuit 154 a, a measurement output circuit 156 a, aconfiguration and diagnostic circuit 160 a, and corresponding interfacecircuits 152 b, 154 b, 156 b, 160 b. The interface circuits 152 b, 154b, 156 b, 160 b can provide hardware interfaces for communication to andfrom their respective circuits 152 a, 154 a, 156 a, 160 a. Theindividual circuits 152 a, 154 a, 156 a, 160 a can communicate selectedinformation on the backplane 150 using protocols running on bussesformed from passive traces extending across the backplane 150.

In one aspect, the measurement processing circuit 152 a can be coupledto an interface circuit 152 b such that sensor signals 104 s received bythe interface circuit 152 b are transmitted directly to the measurementprocessing circuit 152 a. That is, the sensor signals 104 s are nottransmitted to the backplane 150. The sensor signals 104 s can beaccessed by an operator through an output port 162. Multiple measurementprocessing circuits 152 a and interface circuit 152 b can be present, ona one-to-one basis, for receipt of the sensor signals 104 s. Asdiscussed above, the measurement processing circuit 152 a can beconfigured to determine one or more values for the operating parametermeasurements contained within the received sensor signal 104 s. Themeasurement processing circuit 152 a can also compare determined values,and/or measured variables of the enhanced data, to pre-determined alarmconditions in real-time and determine a status for the target 102. Themeasurement processing circuit 152 a can further output signalsrepresenting the measured variables of the enhanced data, the determinedvalues, and the determined statuses to the backplane 150.

The measurement processing circuit 152 a can also format processvariables (e.g., determined values, measured variables of the enhanceddata set, annunciated alarms, etc.) for output to the machine controlsystem 112. As an example, the format can be a current that rangesbetween about 4 mA to about 20 mA (also referred to as 4-20) and isproportional to the determined values and/or measured variable ascompared to a corresponding scale. The machine control system 112 canutilize the process variables for process control of the target 102.

The statuses determined by the measurement processing circuits 152 a canbe retrieved by the relay processing circuit 154 a from the backplane150. The relay processing circuit 154 a can include relays that areprogrammed to actuate based upon received alarm statuses to annunciatean alarm. In one example, relays can actuate based upon a single status.In another example, relays can actuate based upon Boolean expressions(e.g., AND or voting) that combine two or more statuses. The relayprocessing circuit 154 a can also output signals representingannunciated alarms directly to the machine control system 112 forprocess control of the target 102. As an example, the machine controlsystem 112 can shut down operation of the target 102 upon receipt of analarm annunciation. Annunciated alarms can also be used to provideindications and/or to drive into digital input of the machine controlsystem 112, the HMI 114, or historian 116.

The measurement output circuit 156 a can retrieve data such asdetermined values, measured variables of the enhanced data, determinedstatuses, and annunciated alarms from the backplane 150 for transmissionto the internal network 110 a. Upon receipt, the retrieved data can bestored by the historian 116 and/or reviewed by an operator using the HMI114.

The configuration and diagnostic circuit 160 a can receive firstconfiguration commands from the internal network 110 a and transmit thefirst configuration commands to the backplane 150 for use by thecircuits 152 a, 154 a, 156 a, 160 a. The first configuration commandscan provide one or more set points for use by the measurement processingcircuit 152 a in determining statuses. The first configuration commandscan also provide logic instructions and identify statuses to be used bythe relay output circuit 154 a for alarm annunciation. The firstconfiguration commands can further identify data such as determinedvalues, measured variables of the enhanced data, determined statuses,and/or annunciated alarms to be retrieved from the backplane 150 by themeasurement output circuit 156 a and transmitted to the internal network110 a.

The configuration and diagnostic circuit 160 a can also receive secondconfiguration commands from the internal network 110 a. The secondconfiguration commands can identify data such as determined values,measured variables of the enhanced data, determined statuses, andannunciated alarms to be retrieved from the backplane 150 andtransmitted to the external network 110 b for use by the diagnosticsystem 120.

While capable of facilitating protection monitoring and conditionmonitoring of the target 102, in some instances, the architecture ofmonitoring systems such as monitoring system 106 can lack flexibility.In one aspect, placement of the configuration and diagnostic circuit 160a in communication with both the internal and external networks 110 a,110 b can cause delays when updating the second configuration commands.When diagnosing machine problems, it can be desirable to change the datareceived by the diagnostic system 120. However, transmissions to or fromcomponents in communication with the internal network 110 a can bestrictly regulated in order to protect the machine control system 112from unauthorized access. This regulation can include permitting theconfiguration and diagnostic circuit 160 a to transmit data to theexternal network 110 b for condition monitoring but prohibitingtransmission of changes to the second commands from the external network110 b to the configuration and diagnostic circuit 160 a. Instead, anauthorized operator of the machine control system 112 can be required toapprove any changes to the second configuration commands and transmitthe updated second conditioning commands from the internal network 110 ato the configuration and diagnostic circuit 160 a.

In another aspect, directly coupling the interface circuit 152 breceiving the sensor signals 104 s to the measurement processing circuit152 a can limit access of the sensor signal 104 s to only themeasurement processing circuit 152 a. As a result, the other circuits154 a, 156 a, 160 a of the monitoring system 106, as well as thediagnostic system 120, cannot utilize the raw operating parametermeasurements transmitted by the sensor signal 104 s. Furthermore, shoulda second measurement processing circuit (not shown) be added to themonitoring system for receipt of additional sensor signals from anothersensor, each measurement processing circuit could utilize the operatingparameter measurements it receives but not operating parameters receivedby the other.

In a further aspect, process variables output by the measurementprocessing circuit 152 a to the machine control system 112 can belimited. In general, for each sensor signal 104 s received by themeasurement processing circuit 152 a, there can be a variety of possibleprocess variables (e.g., determined values and/or measured variables ofthe enhanced data set). As an example, there can be 8 possible processvariables determined by the measurement processing circuit 152 a from asensor signal 104 s measuring radial vibration (vibration amplitude, gapvoltage, 1× filtered amplitude, 2× filtered amplitude, 1× filteredphase, 2× filtered phase, Not lx amplitude, and Smax. However, themeasurement processing circuit 152 a can possess the ability to output asingle process variable for each sensor 104 from which it receivessensor signals 104 s.

One or more of these limitations can be addressed by embodiments of aflexible monitoring system of the present disclosure. FIG. 2 illustratesan exemplary embodiment of an operating environment 200 including aflexible monitoring system 202. The operating environment 200 can besimilar to the operating environment 100, except that the monitoringsystem 106 is replaced with the flexible monitoring system 202. Theflexible monitoring system 202 can include a base 204 containing abackplane 206, and one or more circuits 210. The backplane 206 can beconfigured to communicatively couple with two or more circuits 210 andreceive data from at least one circuit 210 coupled thereto. As discussedherein, data transmitted to the backplane 206 can be referred to asmonitoring data. In one aspect, monitoring data can include informationcontained within the sensor signals 104 s, such as measured operatingparameters of the target 102 and measured variables of the enhanced dataset. Monitoring data can also include any values, statuses, and/orannunciated alarms that are determined based upon the measured operatingparameters of the target 102 and/or measured variables of the enhanceddata set. Circuits 210 coupled to the backplane 206 can retrievemonitoring data from the backplane 206. In certain embodiments, thebackplane 206 can be passive. A passive backplane can containsubstantially no or no logical circuitry that performs computingfunctions. Desired arbitration logic can be placed on daughter cards(e.g., one or more of the circuits 210) plugged into or otherwisecommunicatively coupled to the passive backplane.

In contrast to the circuits 152 a, 154 a, 156 a, 160 a of the monitoringsystem 106, the circuits 210 can be designed with a common architecturethat is programmable to perform different predetermined functions of theflexible monitoring system 202. Sensor signals 104 s received by one ormore of the circuits 210 can be transmitted to the backplane 206 andmonitoring data represented by the sensor signals 104 s can be accessedby any circuit 210. Furthermore, the flexible monitoring system 202 cancommunicatively couple multiple bases in a manner that forms a commonbackplane 206′ from the individual backplanes 206 of each base 204(e.g., a logical backplane). Thus, circuits 210 can retrieve monitoringdata from any backplane 206 forming the common backplane 206′, ratherthan just from the backplane 206 to which they are physically coupled.

In certain embodiments, the circuits 210 of the flexible monitoringsystem 202 can be configured to provide at least functionality similarto that of circuits 152 a, 154 a, 156 a, 160 a of the monitoring system106. Exemplary embodiments of circuits 210 are illustrated in FIGS. 2-3and discussed in detail below. As an example, circuits 210 can includeinput circuits 210 i, processing circuits 210 p, output circuits 210 o,and infrastructure circuits 210 n. It can be understood, however, thatthe circuits 210 can be programmed to perform other functions.Accordingly, the flexible monitoring system 202 can be configured toreceive sensor signals 104 s and output monitoring signals 206 s, 208 sto the internal and external networks 110 a, 110 b, respectively. Asdiscussed in detail below, embodiments of the flexible monitoring system202 can receive command signals 209 s, 211 s from the internal andexternal networks 110 a, 110 b, respectively, without compromisingsecurity of the machine control system 112. As a result, the flexiblemonitoring system 202 can be a suitable replacement for existingdeployments of monitoring systems 106 while providing improvedflexibility and functionality.

With this architecture, the circuits 210 can be combined in various wayson one or more backplanes 206 to form different implementations of theflexible monitoring system 202. The number of bases 204, input circuits210 i, processing circuits 210 p, output circuits 210 o, andinfrastructure circuits 210 n included in a given implementation of theflexible monitoring system 202 can also be varied independently of oneanother. In some implementations, the flexible monitoring system 202 canbe in the form of a single base 204 including circuits 210 configured toprovide signal input, signal output, protection monitoring, conditionmonitoring, and combinations thereof. In other implementations, theflexible monitoring system 202 can be in the form of at least two bases204 and circuits 210 configured to perform any combination of signalinput, signal output, protection monitoring, and condition monitoringcan be distributed between the at least two bases 204. In this manner,the input, processing, and output capabilities of the flexiblemonitoring system 202, as well as the physical location of differentcircuits 210 of the flexible monitoring system 202, can be tailored tospecific monitoring applications.

Furthermore, implementations of the flexible monitoring system 202 canbe modified after initially deployed to modify the circuits 210 coupledto a given base 204 in the event that the intended monitoringapplication changes. Given their common architecture, circuits 210 canbe easily added to a base 204 having capacity to couple to a new circuit210. Alternatively, one or more new bases 204 can be communicativecoupled to an existing base 204, allowing one or more new circuits 210to be couple to respective backplane(s) 206 of the new base(s) 204 andexpanding the monitoring capabilities of the flexible monitoring system202. In some instances, circuits 210 removed from one base 204 of theflexible monitoring system 202 can be stored in reserve as spares orredeployed to another base 204 of the same or a differentimplementations of the flexible monitoring system 202, which may bebeneficial.

In certain embodiments, input circuits 210 i can be configured toreceive sensor signals 104 s, perform signal conditioning on the sensorsignals 104 s, and output the conditioned sensor signals 104 s to thebackplane 206. In contrast to the monitoring system 106 of FIGS. 1A-1B,the input circuits 210 i can be decoupled from processing circuits 210p, allowing the number of input circuits 210 i of the flexiblemonitoring system 202 to be varied independently of the number ofprocessing circuits 210 p.

The sensor signals 104 s can be received from a variety of differenttypes of sensor 104. Examples of sensor types can include, but are notlimited to, vibration sensors, temperature sensors (e.g., resistancetemperature detectors or RTD), position sensors, and pressure sensors.

Embodiments of the flexible monitoring system 202 can include one ormore input circuits 210 i. As shown in the FIG. 2 , the flexiblemonitoring system 202 includes two input circuits 210 i. Each of theinput circuits 210 i can be in communication with a respective sensor104 for receipt of a corresponding sensor signal 104 s. As an example,one sensor signal 104 s can represent first monitoring data includingmeasurements of a first operating parameter of a first machine component(e.g., acquired by a first sensor). The other sensor signal 104 s canrepresent second monitoring data including measurements of a secondoperating parameter of a second machine component (e.g., acquired by asecond sensor, different from the first sensor). In certain embodiments,the first and second machine components can be the same (e.g., thetarget 102). In other embodiments, the first and second machinecomponents can be different (e.g., the target 102 and a different target[not shown]). Similarly, in some embodiments, the first and secondoperating parameters can be the same operating parameter. In one aspect,this configuration can provide redundancy in case of failure of one ofthe sensors 104. In another aspect, this configuration can be utilizedwhere a desired measurement (e.g., shaft rotation speed) is derived fromtwo sensor measurements coordinated in time (phase). In additionalembodiments, the first and second operating parameters can be different.While two input circuits 210 i have been illustrated and discussed,other embodiments of the monitoring system can include greater or fewerinput circuits.

Different types of sensors 104 can generate sensor signals 104 s indifferent formats, and input circuits 210 i can be programmed to performsignal conditioning appropriate to the different sensor signals 104 sbefore transmitting conditioned sensor signals to the backplane 206.Examples of various types of inputs are illustrated in FIG. 3 . In oneinstance, a sensor signal 104 s received from a position sensor can bereceived by a position input circuit 250. In another instance, a sensorsignal 104 s received from a vibration sensor can be received by avibration input circuit 252. In an further instance, a sensor signal 104s received from a temperature sensor can be received by a temperatureinput circuit 254. In an additional instance, a sensor signal 104 sreceived from a pressure sensor can be received by a pressure inputcircuit 256.

In other embodiments, the input circuit 210 i can be in the form of adiscrete contact circuit 260. The discrete contact circuit 260 caninclude a pair of contacts that can be closed by an external switch orrelay. The pair of contacts can be closed by the machine control system112 or by an operator of the machine control system 112 closing aswitch. The discrete contact circuit 260 can be used to change thebehavior of the flexible monitoring system 202. Examples of behaviorchanges can include, but are not limited to, a different mode of machineoperation, causing the flexible monitoring system 202 to inhibit alarmdetermination, and resetting alarm states.

While the monitoring system 106 can include a discrete contact, it canlack specificity. As an example, changes effected by closing a discretecontact in the measurement system 106 can be effected upon all alarmsgenerated by the measurement system 106. In contrast, because thediscrete contact circuit 260 of the flexible monitoring system 202 canbe separate from the protection processing circuit 264, the discretecontact circuit 260 can be configured to effect only selected alarmdeterminations and/or reset alarm states, or effect all alarms.

In further embodiments, the input circuit 210 i can be in the form of adigital data stream input circuit 262. As an example, the digital datastream input circuit 262 can be configured to receive digital datastreams from the sensor 104, the machine control system 112, and/or atrusted third-party system, as opposed to an analog data stream (e.g.,from sensor 104).

Processing circuits 210 p can be configured to retrieve any data fromthe backplane 206, analyze the retrieved operating parameters, andoutput the results of such analysis. As illustrated in FIG. 3 , certainembodiments of the processing circuits 210 p can be configured toperform protection functions and can be referred to as protectionprocessing circuits 264 herein. In other embodiments, the processingcircuits 210 p can be configured to retrieve selected data from thebackplane 206 and transmit the retrieved information to the diagnosticsystem 120 for performing diagnostic and/or predictive functions (e.g.,condition monitoring) and can be referred to as condition processingcircuits 266 herein.

The number of processing circuits 210 p and input circuits 210 iincluded in a given implementation of the flexible monitoring system 202can be varied independently of the one another. In certain embodiments,processing circuits 210 p can be added to the backplane 206 or removedfrom the backplane to tailor the amount of computing resources availablefor protection monitoring and/or condition monitoring. In otherembodiments, a given processing circuit 210 p can be replaced by anotherprocessing circuit 210 p having greater or less computing power.

Any of these scenarios can be beneficial under certain circumstances,providing computational flexibility to the flexible monitoring system202 that can be tailored to a given application and/or modified asneeded. In one instance, machines having relatively low importance canhave higher cost pressures and lower processing requirements. In thiscircumstance, an implementation of the flexible monitoring system 202can include processing circuits 210 p having processing resourcestailored for cost. In another instance, a particular monitoringapplication can require high processing requirements (e.g., fordetermining values characterizing the measured parameters, for output ofmonitoring data, etc.). In this circumstance, an implementation of theflexible monitoring system 202 can include processing circuits 210 phaving processing resources tailored for processing resources. Thus, thearchitecture of the flexible monitoring system 202 can allow adaptationfor different use cases depending upon the priorities of the intendedmonitoring application.

The protection processing circuits 264 and the condition processingcircuits 266 are discussed below with reference to differentfunctionalities. However, protection processing circuits 264 can beprogrammed to perform any function of the condition processing circuits266. Condition processing circuits 266 can be programmed to performfunctions of the protection processing circuits 264, except fortransmitting data to the backplane 206 and providing local storage. Theability to inhibit the condition processing circuit 266 fromtransmitting data to the backplane 206 can inhibit unauthorizedintrusion and facilitate protection of the internal network 110 a andmachine control system 112.

Protection processing circuits 264 can be configured to retrieveselected monitoring data from the backplane 206 in response to receiptof a protection command. As an example, one or more protection commandscan be transmitted to protection processing circuits 264 in the form ofprotection command signal 209 s received from the internal network 110 a(e.g., from an operator of the machine control system 112). The selectedmonitoring data can include at least a portion of the monitoring datatransmitted to the backplane 206. The monitoring data transmitted to thebackplane can be received from an input circuit 210 i or anotherprotection processing circuit 264. The protection processing circuits264 can also be configured to determine a value characterizing theselected monitoring data and transmit the determined value to thebackplane 206 as additional monitoring data.

The protection processing circuit 264 can be configured to determine astatus for the selected monitoring data based upon a comparison of thedetermined value, another determined value retrieved from the backplane206 (e.g., from another protection processing circuit 264), andcombinations thereof, with one or more predetermined set points.Predetermined set points can correspond to respective alarm conditions(e.g., an Alert condition, a Danger condition, etc.). Continuing theexample above, where the determined value is an amplitude of a radialvibration, the one or more set points can include an Alert set point, aDanger set point that is greater than the Alert set point, andcombinations thereof. In certain embodiments, a single set point can beemployed. Assuming the use of Alert and Danger set points, if the radialvibration amplitude value is less than the Alert set point, the statusof the radial vibration amplitude can be determined as “OK.” If theradial vibration amplitude value is greater than or equal to the Alertset point, the status of the radial vibration amplitude can bedetermined as “Alert.” If the radial vibration amplitude value isgreater than the Danger set point, the status of the operating parametercan be determined as “Danger.” After the status of the selectedmonitoring data is determined in this manner, the protection processingcircuit 264 can transmit the determined status to the backplane 206. Thecondition processing circuit 266 can be configured to retrieve selectedmonitoring data from the backplane 206 and to provide the retrievedmonitoring data to the external network 110 b for use by diagnosticsystem 120. In certain embodiments, the selected monitoring data can beretrieved by the condition processing circuit 266 in response to receiptof a conditioning command. As an example, one or more conditioningcommands can be transmitted to condition processing circuits 266 in theform of conditioning command signals 211 s can be received from theexternal network 110 b. (e.g., from an operator of the diagnostic system120). In turn, the diagnostic system 120 can utilize the retrievedmonitoring data to determine the cause of statuses and/or alarmconditions. Alternatively or additionally, the diagnostic system 120 canalso employ the retrieved monitoring data to predict the development ofstatuses and/or alarm conditions before they arise. In furtherembodiments, the diagnostic system 120 can store the retrievedmonitoring data for subsequent analysis. In additional embodiments, thediagnostic system 120 can transmit the retrieved monitoring data toanother computing device for analysis.

In further embodiments, the condition processing circuit 266 canretrieve selected monitoring data from the backplane 206 based upondetection of a pre-determined status. As an example, the conditionprocessing circuit 266 can retrieve and review statuses generated by theprotection processing circuit 264 to identify a status matching thepre-determined status. The identified status can also include a statustime characterizing the time when the status was determined. Uponidentification of a match, the condition processing circuit 266 canretrieve selected monitoring data including operating parametermeasurements corresponding to the pre-determined status for timedurations before and/or after the status time. In this manner, thediagnostic system 120 can be provided with operating parameterinformation relevant to determining the cause of the status. Thepre-determined statuses and selected monitoring data can be containedwithin the one or more conditioning commands.

The number of condition processing circuits 266 present in the flexiblemonitoring system 202 can be varied independently of the number of inputcircuits 210 i. In certain embodiments, condition processing circuit 266can be added to increase the ability of the flexible monitoring system202 to output monitoring data. As an example, when two or more conditionprocessing circuits 266 are present in the flexible monitoring system202, each can tasked with output of different measured operatingparameters. In another example, two or more condition processingcircuits 266 can output the same measured operating parameters in orderto provide redundancy. Each can be beneficial under certaincircumstances, providing computational flexibility to the flexiblemonitoring system 202. In a further example, condition processingcircuits 266 can be added to implement custom analytics withoutinterfering with standard operation (e.g., when beta-testing a newanalytic).

Output circuits 210 o can be configured to obtain any monitoring datacontained on the backplane 206 in response to receipt of output commands(e.g., contained in the one or more protection command signal 209 sreceived from the internal network 110 a). The output circuits 210 o canfurther output the retrieved monitoring data to the internal network 110a in the form of output monitoring signals 206 s. Examples of monitoringdata retrieved by output circuits 210 o can include, but are not limitedto, operating parameter measurements, the determined values, variablesof the enhanced data set, statuses, and alarms.

With continued reference to FIG. 3 , embodiments of the output circuits210 o can be in the form of proportional output circuits 270. Theproportional output circuits 270 can be configured to output monitoringsignals 206 s in the form of process control signals (not shown). Theprocess control signals can be proportional to process variables, suchas direct measurement values or variables of the enhanced data set, ascompared to a predetermined scale. As an example, a current output canbe a 4-20 mA output. The process control signals can be provided to themachine control system 112, either directly or via the internal network110 a, to facilitate control of operating parameters of the target 102.The process variables included in the process control signals can bespecified by the protection command signal 209 s.

In further embodiments, output circuits 210 o can be in the form of oneor more relay circuits 272 configured to retrieve selected status datafrom the backplane 206 and to actuate based upon received alarm statusesto annunciate an alarm. Annunciated alarms can be output in the form ofalarm signals (not shown). In one example, relays can actuate based upona single status. In another example, relays can actuate based uponpredetermined Boolean expressions (e.g., AND or voting) that combine twoor more statuses. The alarm signals can be provided to the machinecontrol system 112 via the internal network 110 a, or directly to themachine control system 112, to facilitate control of operatingparameters of the target 102. As an example, the machine control system112 can shut down operation of the target 102 in response to receipt ofan alarm signal. The selected status data and the logic employed foractuation of a relay can be specified by the protection command signal209 s.

In other embodiments, output circuits 210 o can be in the form of atleast one communication interface circuits 274. The communicationinterface circuit 274 can be configured to retrieve selected monitoringdata from the backplane 206 in response to receipt of the protectioncommand signal 209 s. The selected monitoring data can include one ormore of the measured operating parameters, the measured variables of theenhanced data set, determined statuses, and determined alarms. Theretrieved data can be transmitted to the internal network 110 a in oneor more output monitoring signals 206 s for use by machine controlsystem 212 (e.g., for process control), the HMI 114 (e.g., display to anoperator) and/or stored by the historian 116.

Infrastructure circuits 210 n can be configured to perform functionalityrequired for the flexible monitoring system 202 to operate. As shown inFIG. 3 , embodiments of the infrastructure circuits 210 n can take theform of a system interface circuit 276. The system interface circuit 276can function as an access point for transmission of protection commandsignals 209 s from the internal network 110 a to the monitoring system220, facilitating configuration of the circuits involved in protectionmonitoring (e.g., protection processing circuit 264, output circuits 210i). The protection command signals 209 s can include one or more signalsincluding any of the following in any combination: identification ofselected monitoring data for each of the protection processing circuit264 and output circuits 210 i to retrieve and/or output, alarm setpoints for the protection processing circuit 264, and logic forannunciation of relays by relay output circuits 272.

It can be appreciated that, in contrast to the monitoring system 106,embodiments of the flexible monitoring system 202 can separate thecircuits 210 that configure protection monitoring functions (e.g., thesystem interface circuit 276) and condition monitoring functionality(e.g., the condition processing circuit 266). As a result, protectionmonitoring configuration can be performed entirely on the internalnetwork 110 a while condition monitoring configuration can be performedentirely on the external network 110 b. That is, the internal network110 a is not communicatively coupled to the external network 110 b. As aresult, conditioning command signals 211 s can be provided to thecondition processing circuit 266 without the need to obtain approvalfrom an authorized operator of the machine control system 112.

In appreciation of cybersecurity risks inherent in allowing thecondition processing circuit 266 to communicate with the externalnetwork 110 b and the backplane 206, the condition processing circuit266 can be limited to unidirectional communication with the backplane206 for data retrieval only. Such unidirectional communication can beestablished by any combination of hardware (e.g., data diodes),firmware, and/or software. In certain embodiments, this unidirectionalcommunication is provided at least through hardware. As a result, theflexible monitoring system 202 can be kept secure from malicious actorswhile facilitating rapid configuration of the condition processingcircuit 266.

In another aspect, infrastructure circuits 210 n can take the form ofpower input circuits 280. Power input circuits 280 can provide theability to connect one or more power sources to the flexible monitoringsystem 202.

In a further aspect, infrastructure circuits 210 n can take the form ofbridge circuits 282. The bridge circuits 282 can provide the ability toconnect the backplanes 206 of two or more bases 204 together and to formthe common backplane 206′ for communication therebetween.

So configured, embodiments of the circuits 210 can be arranged in anycombination distributed amongst one or more bases 204 to formimplementations of the flexible monitoring system having desiredmonitoring capabilities (e.g., input, processing, output, etc.).

FIG. 4 shows a detailed block diagram of a portion of an exemplaryembodiment of a monitoring system 300 that can be configured to monitoroperating parameters of industrial equipment. The monitoring system 300can include any number of functional circuits 310, which can bedetachably coupled to a backplane 306 via ports 308 of the backplane306. The backplane 306 can be, include, or form part of, a physical bus.In some embodiments, the backplane 306 can have a unique ID that can beused to identify the backplane 306. The backplane 306 can be a passivebackplane 306 configured to facilitate multipoint asynchronouselectronic communication between the functional circuits 310 that arecoupled to the backplane 306. Therefore, all data that is delivered tothe backplane 306 can be received by all functional circuits 310 thatare coupled to the backplane 306. In the illustrated example, thebackplane 306 includes a number of data lanes 312 that are in electroniccommunication with ports 308 that are configured to receive functionalcircuits 310. Each port 308 is configured to facilitate electroniccommunication between a functional circuit 310 coupled to the port 308,and all of the data lanes 312 of the backplane 306.

As shown in FIG. 4 , each data lane can include a transmitting portion314 and a receiving portion 316. Ends of the transmitting and receivingportions can be coupled with resistors 318 that extend between thetransmitting and receiving portions 314, 316. The resistors 318 canfunction to prevent, or mitigate, signal reflections that can be causedby unused energy associated with pulsed signals delivered to the datalanes 312 and/or noise due to inductance and capacitance effectsassociated with the data lanes 312. The transmitting and receivingportions 314, 316 of each data lane 312 can be coupled to each port 308to facilitate electronic communication between the functional circuits310 and the data lanes 312. Therefore, each port 308 facilitatesdelivery of data (e.g., data packets) to all data lanes 312, andretrieval of data from all data lanes 312.

There are a number of different types of functional circuits 310 thatcan be coupled do the backplane 306. For example, one or more of thefunctional circuits 310 can be an input circuit, a processing circuit,an output circuit, and/or an infrastructure circuit, as described withregard to FIGS. 2-3 . In some embodiments, each functional circuit 310can have a unique ID (e.g., a MAC address) that can be used to identifythe functional circuit 310. The monitoring system 300 provides a highdegree of flexibility and scalability by allowing a user to adjustperformance of the monitoring system by attaching different functionalcircuits 310 to the backplane. For example, processing power can beincreased by coupling additional processing circuits to the backplane306. As another example, the monitoring system 300 can be expanded bycoupling additional input circuits to the backplane 306 such that themonitoring system 300 can receive and process sensor data fromadditional sensors (e.g., sensors 104) used for monitoring theindustrial equipment.

As shown in the illustrated example, each functional circuit 310 caninclude a circuit controller 320 and a node 322 configured to facilitateand control electronic communication between the circuit controller 320and the backplane 306. For example, the node 322 can control delivery ofdata from the circuit controller 320 to the data lanes 312 of thebackplane 306. The nodes 322 can also control which data is deliveredfrom the data lanes 312 to the circuit controllers 320 of the functionalcircuits 310.

The circuit controllers 320 can include memory, at least one dataprocessor, and/or other circuitry configured facilitate operation asdescribed herein. The circuit controllers 320 can be configured toperform specific operations corresponding to desired functionality ofthe functional circuit 310. In some embodiments, the circuit controllers320 can be configured to receive data from an external source (e.g., asensor, or a user device), process the data, and provide the data to thenode 322. For example, if a given functional circuit is an inputcircuit, as described herein with regard to FIGS. 2-3 , the circuitcontroller 320 can include an analog-to-digital (A/D) converter that canbe configured to receive analog signals from sensors and convert theanalog signals to digital signals. Each of the circuit controllers canbe configured to receive data from all data lanes of the backplane(e.g., via the node 322) and process the data.

In some embodiments, circuit controllers 320 of functional circuits 310such as, e.g., protection circuits, can be configured to retrieve anydata packets (e.g., data packets corresponding to sensor measurements)from data lanes 312 of the backplane 306 (e.g., via the node), analyzethe retrieved data packets, and provide the results of such analysis tothe data lanes 312 of the backplane 306 (e.g., via the node). Forexample, circuit controllers 320 of protection circuits can also beconfigured to compare data received from the backplane to pre-determinedalarm conditions in real-time and determine a status (e.g., OK, alert,danger, etc.) for any measured operational parameter or variable, aloneor in combination. The determined status can be subsequently output tothe data lanes 312 of the backplane 306. Circuit controllers 320 ofcondition monitoring circuits can generally function similarly tocircuit controllers of protection circuits. However, nodes of conditionmonitoring circuits can prevent the circuit controllers 320 of thecondition monitoring circuits from delivering data to data lanes 312 ofthe backplane 306, as described in more detail below.

In some embodiments, circuit controllers 320 of output circuits (e.g.,output circuits 210 o) can be configured to obtain any data packetsdelivered to the data lanes 312 of the backplane 306, and outputmonitoring signals (e.g., monitoring signals 106 s) to any externalsystems (e.g., external systems 110). Examples can include, but are notlimited to, the direct measurement values, variables of an enhanced dataset, and statuses, 4-20 mA recorder outputs, voltages of directmeasurement values, as described herein with regard to output circuits210 i. In some embodiments, circuit controllers 320 of output circuitssuch as, e.g., relays, can be configured to retrieve status data fromdata lanes 312 of the backplane 306 (e.g., via the node) and to actuatebased upon received data characterizing alarm statuses. In one example,circuit controllers 320 of relay circuits can actuate based upon asingle status. In another example, relay circuits can actuate based uponBoolean expressions (e.g., AND or voting) that combine two or morestatuses. In some embodiments, upon actuation, relay circuits can beconfigured to deliver a monitoring signal (e.g., monitoring signal 106s) to a control system (e.g., customer control system 212). The controlsystem can then stop operation of the equipment being monitored toprevent damage or failure.

Circuit controllers 320 of infrastructure circuits (e.g., infrastructurecircuits 210 n) can be configured to perform operations required for themonitoring system to function. For example, circuit controllers 320 ofsystem interface circuits can function as an access point forconfiguration of any of the functional circuits, alarm conditions forprotection of the industrial equipment, and conditions for actuation ofrelay circuits. In some embodiments, circuit controllers 320 of systeminterface circuits can be coupled to the control system and/or a HMI(e.g., HMI 220). A trusted user, such as, e.g., a plant operator, canprovide configuration data to the circuit controller 320 of the systeminterface circuit via the control system and/or the HMI, and the systeminterface circuit can provide data packets characterizing theconfiguration data to data lanes 312 of the backplane 306.

As described herein, the circuit controllers 320 can be configured toprovide data to the nodes 322, but the circuit controllers do not havedirect control of data delivery to the data lanes 312. The nodes 322 ofthe functional circuits 310 can control data flow between the circuitcontrollers 320 and the data lanes 312. Each node 322 can include a nodecontroller 324, a gate controller 326, as well as an array of gate pairs328. The gate pairs 328 can be configured to facilitate electroniccommunication between the functional circuits 310 and the data lanes 312of the backplane 306. Each gate controller 326 can be configured tocontrol operation of transmitters 330 and receivers 332 of thecorresponding functional circuit 310, thereby controlling data flowbetween the functional circuit 310 and the data lanes 312 of thebackplane 306. The transmitters 330 and receivers 332 can be referred toas gates. The transmitters 330 and receivers 332 are described in moredetail below.

The node controllers 324 can include memory, at least one dataprocessor, and/or other circuitry configured facilitate operation asdescribed herein. Each node controller 324 can be in electroniccommunication with the circuit controller 320 gate controller 326 of thecorresponding functional circuit 310. The node controller 324 canfunction as an interface between the circuit controller 320 and the gatecontroller 326 and/or the transmitters 330 and receivers 332. Forexample, the node controller 324 can be configured to control which datais transferred from the data lanes 312 to the circuit controller 320using, e.g., packet filtering techniques. As an example, a circuitcontroller 320 of a functional circuit 310 such as, e.g., a protectioncircuit, can send a signal to the node controller 324 to instruct thenode controller to provide specific data from the backplane 306. Thenode controller 324 can monitor data lanes 312 of the backplane 306,identify the desired data packets, and deliver the data packets and/or,data corresponding to the data packets, to the circuit controller 320for processing. In some embodiments, the node controllers 324 can useinformation provided with data packets delivered to the backplane toidentify relevant data to provide to the circuit controller 320. Forexample, the node controller can use IP addresses, MAC addresses, TCP/IPheaders, UDP/IP headers, message headers, object headers, sourceinformation. destination information, and/or contents of the datapackets to identify relevant data packets to provide to the circuitcontroller 320. In some embodiments, the node controller 324 can beconfigured to receive signals from the circuit controller 320, encodethe signals into bits, and deliver signals (e.g., data packets)corresponding to the encoded bits to the gate controller 326 for thedata to be delivered to data lanes 312 of the backplane 306. The nodecontroller 324 can also store a copy of a schedule that can be used tocontrol operation of the transmitters 330 and receivers 332.

The gate controllers 326 can include memory, at least one dataprocessor, and/or other circuitry configured facilitate operation asdescribed herein. Each gate controller 326 can be in electroniccommunication with the transmitters 330, receivers 332, and the nodecontroller 324 of the corresponding functional circuit 310. Each gatecontroller 326 can be configured to control operation of thetransmitters 330 and the receivers 332 of the corresponding functionalcircuit 310, thereby controlling data flow between the functionalcircuit 310 and the data lanes 312 of the backplane 306. For example,the gate controllers 326 can control operating modes of the gate pairs328. In some embodiments, the gate controllers 326 can be configured tocontrol operating modes of the transmitters 330 and receivers 332 basedon a predetermined schedule and/or instruction provided by the nodecontroller 324. As an example, the gate controllers 326 can beconfigured to receive data from the node controller 324, store the data,and deliver it to the data lanes 312 at a scheduled time. In someembodiments, the gate controller 326 can receive the schedule from thenode controller 324. The schedule, as well as operating modes of thetransmitters 330 and receivers 332, are described in more detail below.In some embodiments, each data lane 312 can have a correspondingschedule that defines when the various functional circuits 310 candeliver data packets to that particular data lane 312.

As shown in the illustrated example, the gate pairs 328 can beelectrically coupled to individual data lanes 312 via the ports 308. Insome embodiments, each gate pair 328 can be a half-duplex transceiverthat includes a transmitter 330 and a receiver 332. The transmitters andreceivers can be referred to as gates. Each transmitter and receiver ofeach gate pair 328 can be electrically coupled to receiving andtransmitting portions 316, 314 of a corresponding data lane 312,respectively. In some embodiments, the node controller 324, gatecontroller 326, transmitters 330 and/or receivers 332 can be a fieldprogrammable gate array (FPGA).

The transmitters can be configured to facilitate delivering signalscorresponding to data packets to data lanes of the backplane. Eachtransmitter can have first and second operating modes. When in the firstoperating mode, the transmitters are configured to allow data (e.g.,data packets) to be transferred from the functional circuits 310 to thedata lanes 312 of the backplane 306. In some embodiments, the gatecontroller 326 can deliver control signals to the transmitters to setthem to operate in the first operating mode. As an example, the controlsignal can be an electrical signal delivered to the transmitters. Asanother example, the control signal can be a change in a voltage and/orcurrent of an electrical signal delivered to the transmitters. When inthe second operating mode, the transmitters are configured to preventdata (e.g., data packets) from being transferred from the functionalcircuits 310 to the data lanes 312 of the backplane 306. For example,when in the second operating mode, the transmitters can be logicallydisconnected from the port 308 and from the corresponding data lane 312of the backplane 306. When in the second operating mode, thetransmitters can have a high impedance to prevent signals from beingdelivered to the data lanes 312 of the backplane 306. For example, thegate controller 326 can deliver control signals to the transmitters suchthat the transmitters have a high impedance, thereby preventing thetransmitters from delivering data packets to the data lanes 312. Asanother example, the gate controller 326 can stop delivering electricalsignals to the transmitters 330, thereby placing the transmitters 330 ina state of high impedance. Operating modes of each transmitter can becontrolled independently by the gate controllers 326 of the functionalcircuits 310.

The receivers can facilitate receiving signals corresponding to datapackets from data lanes 312 of the backplane 306. In some embodiments,the receivers can be configured to modify and/or control signalsdelivered to the circuit controller 320 from the backplane. For example,the receivers can receive signals from the data lanes 312 of thebackplane 306, amplify the signals, and provide the signals to thecircuit controller 320 (e.g., via the gate controller 326 and/or thenode controller 324).

In some embodiments, the receivers can also have first and secondoperating modes. When in the first operating mode, the receivers can beconfigured to allow data (e.g., data packets) to be transferred from theattached data lane 312 to the node controller 324 and/or the circuitcontroller 320. When in the second operating mode, the receivers can beconfigured to prevent data (e.g., data packets) from being transferredfrom the attached data lane 312 to the node controller 324 and/orcircuit controller 320. As an example, if the gate pairs 328 arehalf-duplex transceivers, when the transmitter is in the first operatingmode, the receiver is in the second operating mode. In some embodiments,when the transmitter switches to the first operating mode, thetransmitter can deliver a control signal to the receiver to switch thereceiver to the second operating mode. Conversely, when the transmitteris in the second operating mode, the receiver is in the first operatingmode. As an example, when the transmitter switches to the secondoperating mode, the transmitter can stop delivering the control signalto the receiver, thereby switching the receiver to the first operatingmode.

In some embodiments, operating modes of the receivers can be controlledindependently of the corresponding transmitter of the gate pair 328. Forexample, the gate controller 326 can deliver a control signal to thereceivers to put the receivers in the second operating mode.Periodically, at predetermined times, the gate controller 326 can stopdelivering the control signal to the receivers, thereby switching thereceivers to switch to the first operating mode.

In order to effectively manage communication between each of thefunctional circuits 310, a communication schedule can be created anddistributed among the functional circuits 310. In an exemplaryembodiment, at least one node 322 of one of the functional circuits 310can include a schedule controller 334 that can be part of, and/or inelectronic communication with, the node controller 324. The schedulecontroller 334 can include memory, at least one data processor, and/orother circuitry configured facilitate operation as described herein. Theschedule controller can be configured to generate schedules that candefine when each of the transmitter and/or receivers are in the first orthe second operating modes. Therefore, the schedule determines when eachfunctional circuit 310 can deliver data to each data lane 312 of thebackplane 306. Controlling operating modes of the transmitters 330 andreceivers 332 can be referred to as gating. Each schedule can include aframe that corresponds to a predetermined amount of time. The frame canbe divided into a number of time slices. Each time slice can be assignedto a given functional circuit 310, thereby allowing the functionalcircuit 310 to deliver data to the data lanes 312 during assigned timeslice. Schedule generation can also be referred to as arbitration.Functional circuits 310 that are capable of generating schedules anddelivering the schedules to the data lanes 312 can be referred to asarbitration capable functional circuits. The functional circuit 310 thatis in control of generating the schedule can be referred to as a mastercircuit. The node 322 of the master circuit can be referred to as amaster node, or a manager node. Other functional circuits 310 that arecoupled to the backplane 306 can be referred to as slave circuits. Themaster circuit can be in a master/slave relationship with all otherfunctional circuits (e.g., the slave circuits) that are coupled to thebackplane 306. Nodes 322 of the slave circuits can be referred to asslave nodes.

In some embodiments, gating can be autonomously arbitrated betweenfunctional circuits 310 of the monitoring system 300. For example, uponinitial system startup, the functional circuits 310 can wait for apredetermined period of time to receive a beacon packet indicating thepresence of a master circuit. If the functional circuits 310 do notreceive a beacon packet after the predetermined period of time, afunctional circuit 310 that is capable of arbitration can deliver abeacon packet to the data lanes 312 indicating that it (the arbitrationcapable functional circuit 310) has assumed arbitrationresponsibilities, thereby becoming the master circuit.

To generate the schedule, the schedule controller 334 of the mastercircuit can start a schedule record in memory. The schedule controller334 can then provide the node controller 324 with a signal to deliver abeacon packet to data lanes 312 of the backplane 306. The beacon packetcan contain information about the monitoring system 300 (e.g., uniqueIDs) schedule for the current frame. The beacon packet can also includetime syncing information that each of the slave circuits can use tosynchronize internal clocks with that of the master circuit. Timesynchronization can allow functional circuits 310 to effectivelycommunicate over shared data lanes 312 at predetermined scheduled times.The beacon signal can also trigger slave circuits to request time sliceswithin the following frame. Each slave circuit can deliver a beaconresponse packet to the data lanes 312 to request certain time slices todeliver data to the backplane 306. For example, node controllers 324 cangenerate beacon packets to request time slices based on requestsreceived from the circuit controllers 320.

The schedule controller 334 of the master circuit can receive therequests and can assign time slices to various nodes 322 and/orfunctional circuits 310, thereby generating the schedule. The schedulecontroller 334 can deliver the schedule to the node controller 324,which can provide the schedule to the gate controller 326. The gatecontroller 326 can deliver the schedule to the data lanes 312 of thebackplane 306 at predetermined time slices, which can be referred to asbeacon time slices, via the transmitters. Each slave circuit can receivethe schedule from the backplane 306, and implement the schedule. Forexample, gate controllers 326 of each functional circuit 310 can receivethe schedule and can enforce the schedule by controlling operating modesof the transmitters 330 and receivers 332 based on what is definedwithin the schedule.

In some embodiments, the gate controller 326 of each node 322 canlogically disconnect the transmitters from the data lanes 312 duringtime slices that are not assigned to that particular node 322. In thisway, circuit controllers 320 of slave circuits can request certain timeslices within the schedule, but the circuit controllers 320 have nodirect control over the transmitters 330 and receivers 332 of thefunctional circuit 310. As such, the circuit controllers 320 have nodirect control over when data can be delivered to the data lanes 312.Therefore, if a functional circuit is sending invalid data, e.g., due toaccidental or intentional corruption, the functional circuit 310 onlycorrupt time slices that have been scheduled for that particularfunctional circuit 310.

During normal operation, the gate controller 326 of a given functionalcircuit 310 can operate all of the transmitters 330 in the firstoperating mode during time slices that are assigned to that particularfunctional circuit 310. During assigned time slices, the gate controller326 can provide data to all of the data lanes simultaneously. Forexample, if the backplane 306 includes 16 data lanes, the gatecontroller 326 can transmit a 2 bytes of information by simultaneouslytransmitting 1 bit of information to each data lane via the transmitters330.

In some embodiments, one or more of the slave circuits can be configuredto assume arbitration responsibilities if the master circuit is disabledor removed from the backplane. For example, if the slave circuits do notreceive a beacon signal at the beginning of a frame, an arbitrationcapable slave circuit can wait for a period of time before delivering abeacon packet to the data lanes 312 indicating that it (the arbitrationcapable slave circuit) has assumed arbitration responsibilities, therebybecoming the master circuit. Methods of generating the schedule, andcommunication between master circuits and slave circuits, are discussedin more detail below.

Since arbitration can be performed by multiple functional circuits 310,and gating can be managed by nodes 322 of each functional circuit 310rather than by a centralize source on the backplane 306, the monitoringsystem 300 provides robust communication between functional circuits 310without a single point of failure. The method of arbitration isdiscussed in more detail below.

The functional circuits 310 can vary in a number of ways. For example,in some embodiments, one or more functional circuits can includemultiple nodes for redundancy. FIG. 5 shows an example of a functionalcircuit 310 a that can generally be similar to the functional circuits310 shown in FIG. 4 , but that includes a primary node 322 and asecondary node 323. The functional circuit 310 a can include a circuitcontroller 320 that can be in electronic communication with nodecontrollers 324 of the nodes 322, 323. The primary and secondary nodes322, 323 can include the node controllers 324, schedule controllers 334,gate controllers 326, and gate pairs 328 that can include transmitters330 and receivers 332, which can be transmitters and receivers,respectively. The functional circuit 310 a can be coupled to a port(e.g., port 308) of a backplane (e.g., backplane 306), and can functionas described above with regard to the functional circuits 310 shown inFIG. 4 . However, in this case, during operation one of the primary andsecondary nodes 322, 323 can be disabled while the other of the primaryand secondary nodes 322, 323 is operable. If the operable node 322, 323fails, the other node 322, 323 can be activated to ensure that thefunctional circuit 310 a can send data to, and receive data from, datalanes of the backplane. In some embodiments, the port of the backplanecan couple corresponding gate pairs 328 of the individual nodes to thesame data lane of the backplane, thereby allowing a seamless transitionto the secondary node 323, if the primary node 322 fails.

In some embodiments, a monitoring system can include functional circuitsthat can be prevented from delivering data to the data lanes of thebackplane. As an example, a functional circuit such as, e.g., acondition monitoring circuit, can be configured to receive data fromdata lanes of a backplane, but can be prevented from delivering data tothe data lanes of the backplane. FIG. 6 shows an example of a functionalcircuit 310 b that is configured to receive signals from data lanes of abackplane, but is prevented from delivering signals to the data lanes ofthe backplane. As shown in the illustrated example, the functionalcircuit that includes a circuit controller 320 and a node 325 that isconfigured to facilitate communication between the circuit controller320 and data lanes of the backplane. The node 325 includes a nodecontroller 324, a gate controller 326, receiver 332 such that it canreceive signals from data lanes of a backplane, but does not includetransmitters 330, thereby preventing the functional circuit 310 b fromdelivering signals to the data lanes of the backplane.

In some embodiments, the functional circuit 310 b can allow anuntrusted, or external, user to view information from the backplane andinteract with the circuit controller 320. An example of such a user canbe, e.g., a remote maintenance engineer. As an example, the user candeliver data to the circuit controller 320 to request specificinformation (e.g., sensor data) from the data lanes for troubleshootingpurposes. The circuit controller 320 can deliver the request to the nodecontroller 324, which can allow the desired data to be delivered fromthe data lanes to the circuit controller 320. The user can review thedata and assist a plant operator with troubleshooting, but cannotdeliver any data to the data lanes of the backplane. Therefore, the usercannot make any changes to a monitoring system that employs thefunctional circuit 310 b. The user can only relay information to theplant operator which, as a trusted user, can make changes to themonitoring system.

Controlling when each circuit module can communicate can provide a highdegree of synchronization and determinism, which can facilitatecommunication between functional circuits without centralized switchingwithin the bus. By utilizing functional circuits that can generatecommunication schedules, in conjunction with one or more bus that allowseach of the functional circuits to communicate information to eachother, the monitoring system 300 provides a modular, flexible, andscalable solution for monitoring industrial equipment.

Traditional monitoring systems can be limited in terms of flexibilityand scalability. Additionally, costs and complexity of installation cancreate a significant barrier to entry for users that want to monitor lowcost and/or low priority components/systems. By utilizing functionalcircuits that can be detachably coupled to the backplane, performance ofthe monitoring systems described herein can be adjusted and/or scaled tofit individual monitoring needs. For example, processing power can beincreased by coupling additional processing circuits to the backplane.As another example, the monitoring system can be expanded by couplingadditional input circuits to the backplane to such that the monitoringsystem can receive and process sensor data from additional sensors.Additionally, by generating a schedule at a master circuit, and gatingcommunications at slave circuits, the monitoring system can providerobust communication and/or eliminate centralized failure pointsassociated with system that use centralized switching for communication.

Since functional circuits can send and receive signals via one or moredata lanes in a bus, it can be desirable to configure functionalcircuits (e.g., functional circuits 310) to broadcast data based on aschedule. Doing so can prevent multiple functional circuits frombroadcasting simultaneously resulting in reduction of collision betweendata packets broadcasted by different functional circuits. FIG. 11illustrates an exemplary time sequencing of communication betweenfunctional circuits of a monitoring system. The monitoring system timecan be divided into system frames during which functional circuitcommunication can be carried out based on a system frame schedule.

As illustrated in FIG. 7 , system time 402 can be divided into systemframes 404A-N. A system frame 404A can extend over a period of time, forexample, between a starting time 406 and an ending time 408. The systemframe can be divided into multiple time slices 410A-410N that can betemporally contiguous. The first time slice 410A can begin at thestarting time 406 which can be used as a reference time for the systemframe. A second time slice 410B can be temporally adjacent to the firsttime slice 410A. The first time slice 410A can be referred to as abeacon time slice. The second time slice 410B can be referred to as abeacon response time slice. Together, time slices 410A and 410B canconstitute an arbitration period 411 during which a master circuit caninteract with slave circuits for allocation of time slices for datacommunication over the data lanes of the bus. The remaining time slices410C-410N can constitute a data communication period during which slavecircuit can broadcast data packets on the data lanes of the bus.

During the first time slice 410A of the arbitration period 411, themaster circuit can broadcast a beacon packet on a data lanes of the busto which the master circuit is communicatively coupled. The beaconpacket can be received by the slave circuits (e.g., node controllers ofthe slave circuits) that are communicatively coupled to the data lane.The beacon packet can include a system frame schedule for the systemframe 404A that allocates time slices of the data communication period(e.g., time slices 410C-410N) to slave circuits of the monitoringsystem. System frames can also be referred to as frames.

During the second time slice 410B of the arbitration period 411, one ormore slave circuits can broadcast beacon response packet on the datalane of the bus. As an example, node controllers (e.g., node controller324) can generate beacon response packets and deliver the beaconresponse packets to the data lane via transmitters (e.g., transmitters330). The master circuit can receive the beacon response packets fromthe slave circuits. The beacon response packets can include requests fortime slice assignment. The master circuit can generate schedules forfuture system frames (e.g., system frames 404B-N) that can include timeslice assignments based on the requests in the beacon response packetsfrom the slave circuits.

During the data communication period (e.g., 410C-410N), the slavecircuits can broadcast data packets on the data lane of the bus. A slavecircuit can receive the beacon packet broadcasted by the master circuitduring the arbitration period 411, and can broadcast data packets duringthe time slice assigned to it in the system frame schedule of the beaconpacket.

For example, the gate controller in the slave circuit can configure theslave bus node to transmit data packets during the time slice assignedto the slave circuit. This can be done by operating one or moretransmitters in the slave bus node in a first operating mode where thetransmitters allow data packets to be transferred from the slave circuitto one or more data lanes in the bus.

As illustrated by an expanded view of time slice 410G, each time slice410A-410N can include a usable time slice period 420 temporally locatedprior to a dead band period 424. A slave circuits can be configured totransmit data packets during the usable time slice period of theassigned time slice. . As an example, the usable time slice period 420can be used to transmit a data packet that includes a preamble 426,headers 428, 430, 432, a data payload 434, a cyclic redundancy check(CRC) 436, and an interpacket gap 438. As an example, the headers 428,430, 432 can be an Ethernet header, an IP header, and a UDP header,respectively. In some embodiments the preamble 426 can be 8 bytes, thedata payload 434 can be 1476 bytes, the CRC 436 can be 4 bytes, and theinterpacket gap 438 can be 12 bytes. Furthermore, in some embodiments,the headers 428, 430, 432 can be 14, 20,and 4 bytes, respectively.Information corresponding to sizes of preamble 126, the data payload134, the CRC 436, and the interpacket gap 438, and the headers 428, 430,432 can be distributed in schedules provided with beacon packets. Thesizes of the various portions of data packets that can be transmittedduring the useable time slice period can vary. Similarly, the durationof the useable time slice period 420 can vary. For example, the durationof the usable time slice period 420 can be determined based on thelargest permissible data packet that can be broadcasted by a slavecircuit and/or rates at which data can be transferred from functionalcircuits. The duration of the useable time slice period 420 can be atleast as long as the amount of time required to transfer a data packetto the backplane. As an example, data packets can be in a range ofapproximately 56-65535 bytes. As another example, time slices havedurations in the range of approximately 2500-13496 nanoseconds (ns).

The slave circuits may not transmit any data packets during the deadband period 424. The dead band periods 424 at the end of each time slice410A-410N can facilitate seamless transitions between data delivery fromfunctional circuits in communication data lanes of a backplane (e.g.,backplane 306). For example, the dead band period 424 can function tomitigate data transmission timing errors due to inaccuracies in timesynchronization between functional circuits, as well as minimize signalcollisions that can result from latencies associated with datatransmission between bridged backplanes. As an example, timesynchronization errors can arise due to signal propagation delay alongdata lanes, propagation delay between bridged backplanes, timesynchronization errors between functional circuits, bit error rate, andthe like. Bridged backplanes are described in more detail below.

In some embodiments, the duration of the dead band period 424 can bedetermined based on a data communication protocol employed in themonitoring system. For example, an Ethernet communication protocol(e.g., TCP/IP, UDP/IP) can require that the dead band period 424 canallow for communication of a 12 byte data packet. In someimplementations, the duration of the dead band period 424 can bedetermined based on expected and/or known time synchronization errors.

FIG. 8 illustrates an exemplary data structure of a beacon packet 500broadcasted by the master circuit during the arbitration period. Thebeacon packet can include a preamble field 501, which can function as areference signal. The slave circuits of the monitoring use the preamblefield 501 to identify the beginning of data within the beacon packet.The beacon packet can also include data fields such as a type field 502,current time field 504, network identification number (ID) field 505,number of lanes field 507, baud rate field 506, schedule header 522, andschedule entries array 524, among others. The type field 502 canindicate that the data packet is a beacon packet 500. In someembodiments, functional circuits coupled to the backplane can use thepreamble field 501 and the type field 502 to identify data delivered tothe backplane. For example, the preamble field 501 can include a datatransmission clock, which functional circuits coupled the backplane canuse to identify data transmitted from a given functional circuit.

The current time field 504 can function as a reference time tosynchronize clocks of the slave circuits. The current time field 504 canbe, e.g., one or more of time of transmission of the beacon packet,starting time 406, ending time 408, and the like. The network ID fieldcan identify a network formed by one or more backplanes and functionalcircuits coupled thereto. In some embodiments, network IDs can begenerated and/or assigned to the monitoring system upon startup. Thenetwork IDs can function to characterize hardware of the monitoringsystem (e.g., unique IDs of functional circuits and/or the backplane,number of data lanes on the backplane, etc.) as well as operatingparameter such as e.g., communication schedules, the baud rate, etc. Insome embodiments, network IDs can provide a means to identify and/orseparate independent networks that get connected unintentionally. Thebaud rate field 506 can include data that characterizes a speeds ofcommunication over the various data lanes of the backplane.

The beacon packet can also include the system frame schedule 520. Thesystem frame schedule 520 can include a schedule header 522 and aschedule entry array 524. The schedule header 522 can includeself-describing information about the schedule. For example, theschedule header 522 can include data characterizing a number of timeslices included in the schedule, a duration of each time slice, aduration of a dead band within the time slice, and identification datathat can be used by node controllers of functional circuits to parsetime slice assignments within the schedule..

FIG. 9 illustrates an exemplary structure of system frame schedule 520.The system frame schedule includes the schedule header 522 and theschedule entry array 524. The schedule entry array 524 can include timeslice assignments of time slices in the system frame (e.g., system frame404A). The data matrix of schedule entry array 524 can include a timeslice array 602 and assignment array 604. Fields of the time slice arraycan be identify the time slices and the fields of the assignment arraycan include the assignment data for the time slice arrays. For example,assignment field of a time slice that has been assigned to a slavecircuit can include unique identification (ID) of the slave circuit. Asan example a unique ID can be, e.g., MAC address. In some embodiments,the schedule entry array 524 can include time slices that are not beassigned to a slave circuit. The schedule entry array 524 can alsoinclude best-effort time slices in which multiple slave circuits canbroadcast a data packet. An assignment field of an unassigned time slicecan have a first predetermined value (e.g., OO-OO-OO-OO-OO-OO). Anassignment field of a best-effort time slice can include a secondpredetermined value (e.g., FF-FF-FF-FF-FF-FF, or OxAA-AA-AA-AA-AA-AA).

In some embodiments, the master circuit can discard any data packetsbroadcasted by slave monitoring nodes during an unassigned time slice.During the best effort time slice any functional circuit coupled to thebackplane of the monitoring system can broadcast a data packet. As anexample, the best effort time slice can be used to communicate lowpriority traffic, asynchronous application layer events (e.g., eventsthat are difficult to schedule). Because multiple functional circuitsare broadcasting during the best effort time slice, data packetscollisions can occur. These collisions can be resolved using, forexample, a CSMA/CD algorithm. In some embodiments, each functionalcircuit can monitor data lanes of the backplane to determine if acollision has occurred. For example, during periods in which afunctional circuit is transmitting data to data lanes of the backplane,a node controller and/or a gate controller of the functional circuit canmonitor the data lanes to determine if data that exists on the backplaneis the same as the data that was transmitted. If the data on thebackplane is different than the data that was transmitted, then the nodecontroller and/or gate controller can determine that a collision hasoccurred.

FIG. 10 illustrates an exemplary data structure of a beacon responsepacket 700 that can be provided to the backplane by a slave circuitduring the second time slice (e.g., 410B) of the arbitration period 411.The beacon response packet 700 can include type field array 701 and thevalue array 703 can include corresponding array 703 of values. The fieldarray 701 can include a data field 702 indicating that data the beaconresponse packet 700 represents a beacon response packet. The field array701 can also include a slave time fields 704 that can include data thatcharacterizes an internal time of the slave circuit. The field array 701can include a unique identification (ID) field 706 that can include datathat characterizes a unique identification corresponding to the slavecircuit. The field array 701 can also include a time slice request field708 that can include data that characterizes a number of time slicesneeded by the slave circuit to broadcast its data packets.

FIG. 11 illustrates an exemplary communication protocol 800 between amaster circuit 801 and a slave circuit 803. The master circuit 801 caninclude data receivers 804A and data transmitters 806A. The slavecircuit 803 can include data receivers 804B and a data transmitters806B. During the time synchronization period 812, nodes of the mastercircuit 801 and the slave circuit 803 can synchronized their time. Forexample, the master circuit 801 can include its reference time (e.g.,reference time 504) in the beacon packet and transmit it to the slavecircuit 803 during the arbitration period (e.g., first time slice of asystem frame) of one or more system frames. The slave circuit can remainin a standby mode and receive the beacon packets in multiple systemframes. The slave monitoring node can synchronize its internal time withthe reference time of the received beacon packet.

During the arbitration period 814 of a system frame, the master circuitcan transmit beacon packets to the slave monitoring nodes (e.g., duringthe first time slice 410A), and can receive beacon response packet fromthe slave monitoring nodes (e.g., during the second time slice 410B).During the data communication period 816, the slave circuit can transmitdata packets to the master circuit based on the system scheduletransmitted in the beacon packet.

FIG. 12 shows an exemplary structure of a data packet 900 that can bedelivered to the backplane (e.g., backplane 306) of a monitoring system(e.g., monitoring system 300) during operation. As shown in theillustrated example, the data packet 900 can include a packet header902, a communication header 904, a protocol header 906, a packetizedmessage header 908, an object message header 910, an object header 912,and an object body 914. In some embodiments, node controllers (e.g.,node controllers 324) and/or gate controllers (e.g., gate controllers926) of functional circuits can use data within the packet header 902and the communication header 904 to characterize and/or identify thedata packet 900. The protocol header 906, packetized message header 908,object message header 910, object header 912, and object body 914 caninclude data corresponding to a payload of the data packet 900. In someembodiments, circuit controllers (e.g., circuit controllers 320) canused data within the protocol header 906, packetized message header 908,object message header 910, and/or object header 912 to characterizeand/or identify data within the data packet 900.

The packet header 902 can include a packet preamble field 916, a typefield 918, packet number fields 920, a length field 922, and a packetCRC field 924. The preamble field 916 can include a data transmissionclock, which functional circuit coupled the backplane can use toidentify the data packet 900. The type field 918 can include data thatdescribes the type of data transmitted within the data packet 900. Forexample, if the data packet was transmitted by an input circuit, thetype field can indicate that the data packet includes sensor data. Thepacket number fields 920 can include data characterizing information fordelivering the data packet. For example, the packet number fields 920can include data characterizing source information and/or destinationinformation. The length field 922 can include data describing a length(e.g., in bytes) of the data packet 900. The packet CRC field 924 caninclude error checking information that can be used by other functionalcircuit to detect unintentional changes in raw data of the packet header902.

The communication header 904 can include an Ethernet header 926, an IPheader 928, and a TCP/UDP header 930. The Ethernet header 926 caninclude data characterizing MAC addresses of the functional circuitand/or the backplane. IP header 928 can include data describing a sourceIP address and/or a destination IP address. For example, the IP header928 can include an IP address of the functional circuit that deliveredthe data packet 900 as well as an IP address of a functional circuitintended to receive the data packet 900. The TCP/UDP header 930 caninclude data describing source and destination ports. For example, theTCP/UDP header 930 can include a port number identifying a port that thefunctional circuit that delivered the data packet 900 is coupled to. TheTCP/UDP header 930 can also include a port number identifying a portcorresponding to that functional circuit that is intended to receive thedata packet 900.

The protocol header 906 can include a message type field 932, a messagelength field 934, and a message CRC field 936. The message type field932 can include data that describes the type of data transmitted withinthe data packet 900. In some embodiments, circuit controllers (e.g.,circuit controller 320) of functional circuits that receive the datapacket can use data within the message type field 932 to identify thetype of data within the data packet 900. The message length field 934can include data describing a length (e.g., in bytes) of a messagewithin the data packet 900. The message CRC field 936 can include errorchecking information that can be used by other circuit controllers offunctional circuits to detect unintentional changes in raw data of themessage.

The packetized message header 908 can include a packet length field 938,packet number fields 940, and a packet CRC field 942. The packet lengthfield 938 can include data describing a length (e.g., in bytes) of thedata packet 900. The packet number fields 940 can include datacharacterizing information for delivering the data packet 900. Thepacket CRC field 942 can include error checking information that can beused by circuit controllers that receive the data packet 900 to detectunintentional changes in raw data of the packet header 902.

The object message header 910 can include an object number field 944.The packet number fields 940 can include data describing a number ofobjects within the data packet 900.

The object header 912 can include an object ID field 946, an object typefield 948, an object length field 950, a timestamp field 952, a statusfield 954, a configuration sequence number field 956, and an object CRCfield 958. The object ID field 946 can include data identifying anobject field 960 of the object body 914. The object type field 948 caninclude data that describes the type of object transmitted within thedata packet 900. The object length field 950 can include data describinga length (e.g., in bytes) of the object within the data packet 900. Thetimestamp field 952 can include data characterizing a time correspondingto when the data packet 900 was delivered to the backplane. The statusfield 954 can include data describing a status of the object within thedata packet 900. The configuration sequence number field 956 can includedata describing a configuration of data within the data packet 900. Theobject CRC field 958 can include error checking information that can beused by circuit controllers that receive the data packet 900 to detectunintentional changes in raw data of the object within the data packet900.

The object body 914 can include an object field 960. The object field960 can include a portion of the payload that corresponds to the objecttransmitted within the data packet 900. For example, the object fieldcan include data from sensors.

Initially, when a functional circuit of a monitoring system is poweredon, the functional circuit (e.g., a node controller) can perform aninitialization process to determine if a master circuit exists and/or toassume arbitration responsibilities to become the master circuit. FIG.13 shows an exemplary flow diagram 1100 that illustrates aninitialization process that can occur when a functional circuit ispowered on. The functional circuit can be powered on at step 1102. As anexample, the functional circuit can be powered on when the monitoringsystem powered on. As another example, the functional circuit can bepowered on when it is coupled to an active monitoring system (e.g., viahot insertion). The functional circuit can wait for a period of time todetect a beacon signal and/or to receive a schedule.

After a period of time, at step 1104, the functional circuit candetermine that no beacon has been detected, that no schedule isavailable, and that the monitoring system does not include a mastercircuit. The functional circuit can also a link state. The link statecan describe a state of connectivity to the backplane.. If the linkstate indicates that there is no link, at step 1106, the functionalcircuit can start a node (e.g., node 322) of the monitoring state togenerate a positive link state. For example, a card controller of thefunctional circuit can deliver a signal to a node controller to startthe node. In some embodiments, the node controller and/or gatecontroller can identify the link state. If there is no link, the nodecontroller and/or gate controller can start the node. If the node islinked to the backplane, at step 1108, the functional circuit canperform a self-evaluation to determine if it is arbitration capable. Forexample, the node controller of the functional circuit can determine ifit includes, or is coupled to, a schedule controller. If the functionalcircuit is not arbitration capable, it can stop the initializationprocess at step 1110.

If the functional circuit is arbitration capable, a schedule controllerof the functional circuit can generate a beacon packet and provide thebeacon signal to the data lanes of the backplane (e.g., via the nodecontroller and transmitters). If the node controller detects acollision, or if the node controller detects a beacon signal from adifferent functional circuit, the schedule controller and/or nodecontroller can enter a state of random back-off at step 1112. At step1112, the schedule controller and/or node controller can wait for aperiod of time to receive a beacon signal from another functionalcircuit.

In some embodiments, functional circuits that are arbitration capablecan each be configured to wait for random amounts of time during step1112. Waiting for random amounts of time can reduce the probability ofmultiple consecutive collisions, thereby allowing a functional circuitto assume arbitration capabilities more quickly. During step 1112, ifthe functional circuit receives a valid beacon packet, the node can stopthe initialization process. If, at any point during operation, a frame(e.g., the frames discussed above with regard to FIG. 7 ) does notinclude a beacon packet, the functional circuit can restart theinitialization process and attempt to become the master circuit. If eachframe includes a beacon packet, the initialization process can remainstopped indefinitely.

If the functional circuit does not detect a beacon signal, at step 1114,the functional circuit can assume arbitration responsibilities, therebybecoming the master circuit. After the functional circuit becomes themaster circuit, the master circuit can generate, distribute, andmaintain schedules that define when each slave circuit of the monitoringsystem can communicate.

FIG. 14 shows a flow diagram 1200 that illustrates a method ofgenerating a schedule based on the communication requests from slavecircuits. As shown in the illustrated example, the master circuit canassume arbitration capabilities at step 1202. At step 1204, the schedulecontroller of the master circuit can generate a schedule and assignbeacon time slice and beacon response time slice (e.g., time slices410A, 410B). The schedule controller can also store the schedule inmemory. At this point, each time slice within the schedule can beunassigned, with the exception of the beacon time slice (e.g., timeslice 410A) and the beacon response time slice (e.g., time slice 410B).As another example, the time slices can be assigned based on apreviously available schedule. Alternatively, if the functional circuitis in a continued state of operation from a previous frame, the methodcan move directly to step 1206.

At step 1206, the master circuit can transmit a beacon packet during thefirst time slice (e.g., time slice 110A). If the master circuit detectthat there was a collision, at step 1207, the master circuit can enter astate of random back-off in which it will wait for a period of timebefore attempting to transmit another beacon packet with an updated datatransmission clock, or timer, which can be used for time synchronizationacross various functional circuits coupled to the backplane.

If a no collision is detected the schedule controller and/or nodecontroller of the master circuit can wait for a beacon response packetfrom one or more slave circuits at step 1208. If there is no beaconresponse packet, or if the beacon response packet is invalid, the mastercircuit can determine that no schedule update is necessary at step 1210.

At step 1212, if the master circuit receives a valid beacon responsepacket from a slave circuit, the schedule controller of the mastercircuit can process time slice requests from the beacon response packet.If there are no time slices available to be assigned, the schedulecontroller can generate an error signal at step 1214. In someembodiments, the schedule controller can deliver the error signal to aplant operator via a gateway circuit. For example, the schedulecontroller can deliver the error signal to the backplane via the nodecontroller and transmitters and receivers of the master circuit. Thegateway circuit can receive the error signal from the data lane, anddeliver the error signal to a user device to inform the user that thebackplane has been overprovisioned. In some embodiments, a user canreplace the backplane with a backplane that includes more data lanes,thereby facilitating a higher volume of data traffic. As anotherexample, a user can replace the backplane with a backplane that isconfigured to transfer data at a higher rate.

If time slices are available for scheduling, at step 1216, the schedulecontroller can update the schedule to accommodate communicationrequested within the beacon response packet. The schedule controller candeliver another beacon packet containing an updated schedule to thebackplane. Slave circuits can receive the beacon packet from thebackplane, and update their schedules.

At step 1218, the schedule controller and/or node controller of themaster circuit can transition to a traffic monitoring, or “garbagecollection” phase, as described in more detail below. In someembodiments, the traffic monitoring phase can occur simultaneously withall scheduling and arbitration functions performed by the mastercircuit.

As mentioned above with regard to step 1212, if the schedule controllerof the master circuit receives a valid beacon response from a slavecircuit, the schedule controller of the master circuit can process thetime slice requests from the beacon response packet. FIG. 15 shows aflow diagram 1300 illustrating an exemplary method of processing timeslice requests from beacon response packets and generating a scheduleentry array (e.g., schedule entry array 524). At step 1302, the schedulecontroller of the master can receive a beacon response packet and beginprocessing time slice requests.

At step 1304, the schedule controller can allocate memory for variable Nand set a value for the variable within memory. The schedule controllercan determine a number of time slices requested from the beacon responsepacket. For example, the schedule controller can evaluate a value (e.g.,a value provided with the number of requested time slices field 708)corresponding to a time slice request field (e.g., time slice requestfield 708) to determine the number of time slices requested. Theschedule controller can then set a value for the variable N to be equalto the number of time slices requested. If the value of N is zero, atstep 1306, the schedule controller can determine that there are no timeslice requests to be processed. The schedule controller can thenterminate processing time slice requests at step 1308.

At step 1310, the schedule controller can allocate memory for a schedulearray (e.g., schedule entry array 524), which can include a time slicearray (e.g., time slice array 602) and an assignment array (e.g.,assignment array 604). Sizes of the time slice array and the assignmentarray can correspond to a predetermined number of time slices within aframe. For example, if there are 100 time slices per frame, the timeslice array and the assignment array can each have 100 elements. Theschedule controller can also allocate memory for an indexing variable M,and set the value of M to be 0.

At step 1312, the schedule controller can check a value of theassignment array at index M, which corresponds to a time slice at indexM of the time slice array. If the value of the assignment array at indexM indicates that the corresponding time slice is unassigned, at step1314, the schedule controller can set the value of the assignment arrayat index M to be equal to a value of a unique ID (e.g., uniqueidentification (ID) field 706) from the beacon response packet (e.g.beacon response packet 700).

At step 1316, the schedule controller can decrement, or reduce, thevalue N by one. If the value of N is equal to zero after step 1316, atstep 1306, the schedule controller can determine that there are no timeslice requests to be processed. If there are no more time slice requeststo be processed, the process can move to step 1320, which is describedin more detail below. If the value of N is not equal to zero after step1316, the schedule controller can increment, or increase, the value of Mby one at step 1320.

If the value of index M of the assignment array indicates that thecorresponding time slice is not unassigned, or is a best effort timeslice, at step 1318, the schedule controller can determine that the timeslice at index M of the time slice array is already assigned. Theschedule controller can then increment, or increase, the value of M byone at step 1320.

At step 1320, the schedule controller can increment, or increase, thevalue of M by 1. If the value of M is less than the number of timeslices within the frame minus one, the process can return to step 1312.If the value of M is greater than the number of time slices within theframe, step 1322, the schedule controller can determine that a schedulerequest failure has occurred. The schedule controller can then terminateprocessing time slice requests at step 1308.

During operation, the master circuit can monitor traffic on the datalanes of the backplane to verify that data transmission is occurringduring assigned time slices. If there is no data transmission during anassigned time slice, the master circuit can determine that the timeslice has been abandoned. The master circuit can free, or unscheduled, atime slice and can reassign the time slice based on requests receivedduring a subsequent beacon response time slice (e.g., beacon responsetime slice 410B).

FIG. 16 shows a flow diagram 1400 of an exemplary traffic monitoring, or“garbage collection”, process that can be used to recover unused timeslices so that they can be reassigned. At step 1402, the schedulecontroller of the master can begin an iteration of the trafficmonitoring process. At step 1404, the schedule controller can allocatememory to for an indexing variable X and set a value for the variablewithin memory. For example, the value of the indexing variable can beset to be equal to a number of beacon time slices plus one. For example,if an assignment array (e.g., assignment array 604) includes a beacontime slice at index 0, and a beacon response time slice at index 1, thevalue of the indexing variable can be set to 2, which corresponds to theindex of the first time slice that has potentially been assigned to aslave circuit.

At step 1404 the schedule controller can also allocate memory for acounter array. The counter array can be the same size as the assignmentarray. Values of elements of the counter array can be set topredetermined idle slice limit. The idle slice limit can describe anacceptable number of consecutive delivery opportunities in which a slavecircuit can remain idle, i.e., not transmit data. A delivery opportunitycan be a time slice to which the slave circuit has been assigned. Forexample, if each slave circuit can remain idle for two consecutivedelivery opportunities, values of each element of the counter array canbe set to two. In some embodiments, if the counter array already existsfrom a previous frame, the schedule controller can reference theexisting counter array. FIG. 17 shows an example of a schedule entryarray 1500 that includes a time slice array 1502, an assignment array1504, a length array 1506, and a counter array 1508.

At step 1406, the schedule controller can determine a value of index Xof the assignment array. If the value of index X of the assignment arrayindicates that a corresponding time slice has not been assigned, theschedule controller can increment, or increase, the value of X by one atstep 1408.

If the value of index X of the assignment array indicates that thecorresponding time slice has been assigned, at step 1410, the schedulecontroller can monitor one or more data lanes of the backplane for asignal from the slave circuit to which the time slice corresponding toindex X of the time slice array has been assigned. If the master circuitdoes not detect a signal from the slave circuit to which the time slicehas been assigned, at step 1412, the schedule controller can decrement,or decrease, the value of index X of the counter array by one. If indexX of the counter array is equal to zero, at step 1414, the schedulecontroller can unscheduled the slave circuit from the time slot. Theschedule controller can then increase the value of X by one at step1408.

After step 1412, if the value of index X of the counter array is greaterthan zero, at step 1408, the schedule controller can increase the valueof X by one. If the master circuit detects a signal from the slavecircuit to which the time slice has been assigned at step 1410, theschedule controller of the master circuit can set the value of index Xof the counter array to the idle slice limit (e.g., one) at step 1418.The schedule controller can then increase the value of M by one at step1408.

After step 1408, if the value of X is less than the number of timeslices in the frame, the process can then return to step 1408. If thevalue of X is equal to the number of time slices in the frame, at step1416, the schedule controller can terminate the traffic monitor processfor the current frame.

By monitoring traffic on data lanes of the backplane, the master circuitcan maximize efficiency of resource (e.g., time slice) utilization byidentifying time slices in which the assigned slave circuit failed tocommunicate, unscheduling the assigned slave circuit, and reassigningthe time slices based on communication requests received in beaconresponse packets.

FIG. 18 shows a flow diagram 1600 illustrating exemplary operation of anode of a slave circuit of a monitoring system (e.g., the monitoringsystem 300). The slave circuit can generally be similar to thefunctional circuit 310 described above with regard to FIG. 4 . However,in some embodiments, the slave circuit may not include a schedulecontroller, or the schedule controller may be inactive.

At step 1602, the slave circuit can be powered on. At step 1604, a nodecontroller can check to determine whether a circuit controller of theslave circuit has provided a request to deliver data to data lanes of abackplane to which the slave circuit is coupled to.

If the node controller determines that the circuit controller has notprovided any additional requests to deliver data to the backplane, atstep 1606, the node controller can wait to receive a beacon packet froma master circuit. After a period of time, if the node controller doesnot receive a beacon packet, the process can return to step 1604 and thenode controller can check to determine if the circuit controller hasprovided a request to deliver data to data lanes of the backplane. Ifthe node controller receives a beacon packet during step 1606, the nodecontroller can update and/or generate an internal copy of a schedulestored in memory based on a schedule provided with the beacon packet atstep 1608. The node controller can also provide the updated/generatedschedule to a gate controller of the slave circuit so that the gatecontroller can control operation of transmitters and/or receivers of theslave circuit to enforce the schedule. The process can then return tostep 1604 and the node controller can check to determine if the circuitcontroller has provided a request to deliver data to data lanes of thebackplane.

If the node controller detects that the circuit controller has requestedthat data be delivered to the backplane, at step 1610, the nodecontroller can prepare a beacon response packet to request time slicesfor communication based on the request from the circuit controller. Forexample, the circuit controller can provide one or more communicationpackets to the node controller to be delivered to the backplane. Thenode controller can determine the total size (e.g., in bytes), and cancalculate a number of time slices required to transmit the communicationpacket based on a baud rate of the monitoring system. The nodecontroller can generate the beacon response packet requesting thecalculated number of time slices. As another example, in someembodiments, the circuit controller deliver a signal to the nodecontroller to request a certain amount of bandwidth (e.g., in bytes persecond) to deliver a desired payload that can be provided with thecommunication packets.

In some embodiments, at step 1612, the node controller can enter ahold-off state in which the node controller waits for period of time. Asan example, the node controller can enter the hold-off state to reducesimultaneous data delivery to the backplane, thereby reducing the riskof collisions between beacon response packets from different functionalcircuits.. At step 1614, the node controller can wait to receive abeacon packet. After the node controller receives the beacon packet fromthe master circuit, at step 1616, the node controller can provide thebeacon response packet to a data lane of the backplane.

If the node controller detects that the beacon response packetexperienced a collision, the node controller can enter a hold-off stateat step 1612. After a period of time, the node controller can wait for abeacon packet (e.g., in a subsequent frame) at step 1614. After the nodecontroller receives the beacon packet, at step 1616, the node controllercan provide the beacon response packet to the data lane of thebackplane.

At step 1618, after the beacon packet is transmitted to the data lane,the node controller can wait to receive a beacon packet. The nodecontroller can then receive the beacon packet from the master circuit.

At step 1620, the node controller can check a schedule provided with thebeacon packet to determine if the requested time were granted. If slavenode was not assigned the time slices that were requested in the beaconresponse packet, the node controller can enter a hold-off state at step1612. The process can then proceed through steps 1614, 1616, 1618. Ifthe slave node was assigned the time slices that were requested in thebeacon response packet, at step 1622, the node controller can providethe schedule and/or instructions with the assigned time slices to thegate controller. The gate controller can control operation of thetransmitters and/or receivers based on the schedule and/or instructions.For example, the gate controller can switch transmitters to the firstoperating mode during assigned time slices. The gate controller canswitch the transmitters to the second operating mode during time slicesin which the slave circuit is not assigned to communicate.

At step 1624, the node controller can determine a link state of the nodeof the slave circuit. If the link state indicates that the node iscoupled to the backplane, the process can then proceed to step 1606, inwhich the node controller can wait to receive a beacon packet from amaster circuit. The process can proceed from step 1606 as describedabove.

By generating a communication schedule at a master circuit, distributingthe schedule to slave circuits, and enforcing the communication at theslave circuits, the monitoring system provides robust communication andeliminates centralized failure points associated with system that usecentralized switching for communication. The scheduled communication canprevent multiple functional circuits from broadcasting simultaneously,which can mitigate or eliminate collisions between data packetsbroadcasted by different functional circuits.

Exemplary technical effects of the subject matter described herein caninclude the ability schedule communications between multiple functionalcircuits such that the functional circuits can effectively communicateover shared data lanes. Other exemplary technical effects include theability to maximize utilization of a limited number of data lanes, andadapt to physical and/or operation changes of the monitoring system. Forexample, by monitoring traffic on data lanes of the backplane, themaster circuit can adapt to physical and/or operation changes of themonitoring system and maximize efficiency of resource (e.g., time slice)utilization by identifying time slices in which assigned slave circuitsfailed to communicate, unscheduling the assigned slave circuits, andreassigning the time slices based on communication requests received inbeacon response packets.

In some embodiments, multiple backplanes can be coupled using bridgemodules. The coupled backplanes can form an extended logical bus suchthat all data is transferred between the backplanes. This allowsmonitoring systems to span across multiple locations while retaining thefull functionality that is available when using monitoring systems thatinclude a single backplane.

FIG. 19 shows an example of a bridge circuit 1710 that can be configuredto facilitate electronic communication between backplanes of amonitoring system. The bridge circuit 1710 can include a bridgecontroller 1703 that is in electronic communication with a rangeextending element 1705 and a node 322. The nodes 322 can be configuredto facilitate and control electronic communication between the bridgecontroller 1703 and a first backplane of a first monitoring system. Forexample, the node 322 can control delivery of data from the bridgecontroller 1703 to the data lanes of the first backplane.

The node 322 can include a schedule controller 334, node controller 324,gate controller 326, and a gate array that includes gate pairs 328. Thenode controller 324 can include memory, at least one data processor,and/or other circuitry configured facilitate operation as describedherein. The node controller can function as an interface between thebridge controller 1703 and the gate controller 326, transmitters 330and/or receivers 332 of the gate pairs 328. For example, in someembodiments, the node controller 324 can be configured to receivesignals from the bridge controller 1703, encode the signals into bits,and deliver signals corresponding to the encoded bits to the gatecontroller 326 for the data to be delivered to data lanes of the firstbackplane. The node controller 324 can also store a copy of a schedulethat can be used to control operation of the transmitters 330 andreceivers 332. The transmitters 330 receivers 332 and the gatecontroller 326 are described in more detail below.

The gate controller 326 can include memory, at least one data processor,and/or other circuitry configured facilitate operation as describedherein. The gate controller 326 can be in electronic communication withthe transmitters 330, receivers 332, and the node controller 324 of thebridge circuit 1710. The gate controller 326 can be configured tocontrol operation of the transmitters 330 and receivers 332 bridgecircuit 1710, thereby controlling data flow between the bridge circuit1710 and the data lanes of the first backplane. For example, the gatecontroller 326 can control operating modes of the gate pairs 328. Insome embodiments, the gate controllers 326 can be configured to controloperating modes of the transmitters 330 and receivers 332 based on apredetermined schedule and/or instruction provided by the nodecontroller 324. As an example, the gate controller 326 can be configuredto receive data from the node controller 324, store the data, anddeliver it to the data lanes at a scheduled time. In some embodiments,the gate controller 326 can receive the schedule from the nodecontroller 324.

Each transmitter 330 and receiver 332 of each gate pair 328 can beelectrically coupled to receiving and transmitting portions of acorresponding data lane, respectively. In some embodiments, the nodecontroller 324, gate controller 326, transmitters 330, and/or receivers332 can be a field programmable gate array (FPGA). The transmitters 330and receivers 332 can have first and second operating modes, asdescribed above with regard to the transmitters and receivers shown inFIG. 4 .

In some embodiments, the bridge circuit 1710 can include the schedulecontroller 334 such that the bridge circuit 1710 is arbitration capable.The schedule controllers 334 can allow the bridge circuit 1710 to assumearbitration responsibilities and become a master circuits of themonitoring system. The schedule controller 334 can include memory, atleast one data processor, and/or other circuitry configured facilitateoperation as described herein. The schedule controller 334 can beconfigured to generate schedules that can define when each of thetransmitter and/or receivers of functional circuits and/or bridgecircuits 1710 of the monitoring system are in the first or the secondoperating modes. As described here, the schedule identifies when eachfunctional circuit and/or bridge circuit can deliver data to each datalane of the first backplane.

As shown in the illustrated example, the bridge controller 1703 can beelectrically coupled to the range extending element 1705 as well as thenode controller 324 of the node. The bridge controller 1703 can includememory, at least one data processor, and/or other circuitry configuredfacilitate operation as described herein. In some embodiments, thebridge controller 1703 can be, or can include, a FPGA. The bridgecontroller 1703 can be configured to receive data from the firstbackplane (e.g., via the node), process the data, and provide the datato another bridge circuit coupled to a second backplane. For example,the bridge controller 1703 can convert, or condense, parallel data flowfrom data lanes of first backplane to a serial data stream to deliver tothe bridge circuit 1710 coupled to the second backplane, via the rangeextending element. As another example, the bridge controller 1703 can beconfigured to receive a serial data stream from the bridge circuit 1710coupled to the second backplane, and convert serial data stream toparallel data streams to be delivered to data lanes of the firstbackplanes (e.g., via the node).

In some embodiments, the bridge controller 1703 and/or node controllers324 of the bridge circuits 1710 can be configured to store informationabout the monitoring system in memory. For example, the bridgecontroller 1703 can store hardware data, schedules, network IDs, etc. Asan example, hardware data can be, or can include, a unique ID (e.g., aMAC address) of the first backplane and/or functional circuits coupledthereto. As another example, the hardware data can include datadescribing the number of data lanes that the backplane includes. In someembodiments, the bridge controllers 1703 can receive data describing thenumber of data lanes from beacon packets (e.g., number of lanes field207).

The range extending element 1705 can be, or can include, e.g., a signalamplifier and/or attenuator. The range extending element 1705 can beconfigured to facilitate communication between bridge circuits 1710 thatare separated by a range of distances. For example, the range extendingelement 1705 can be configured to receive a signal from the bridgecontroller 1703, amplify the signal, and provide the amplified signal toanother bridge circuit 1710. In some embodiments, the range extendingelement 1705 can be configured to amplify outgoing signals (e.g.,signals delivered to another bridge circuit 1710) based on a knowndistance between the bridge circuits 1710. Additionally, the rangeextending element 1705 can be configured to receive an amplified signalfrom another bridge circuit 1710, attenuate the signal, thereby reducinga voltage and/or current of the signal, and provide the attenuatedsignal to the bridge controller 1703. As an example, the range extendingelement 1705 can attenuate incoming signals (e.g., signals received fromanother bridge circuit) based on predetermined maximum voltage and/orcurrent thresholds for signals that the bridge controller 1703 isconfigured to receive.

In some embodiments, the bridge circuit 1703 can be configured verifythat the monitoring system that are being bridged are compatible. As anexample, the bridge circuit 1703 can use hardware data, unique IDs, andschedules to determine that that monitoring systems are compatible. Oncethe bridge controllers 1703 of the bridge circuit 1710 determine thatthe monitoring systems are compatible, the bridge controllers 1703 canallow the monitoring systems to be connected, thereby facilitatingcommunication between the backplanes of the monitoring systems. Thebridge circuits 1710 are described in more detail below.

FIG. 20 shows a block diagram of an exemplary embodiment of a monitoringsystem 1800 that includes two monitoring subsystems 1801 a, 1801 b thatare coupled using bridge circuits 1710 a, 1710 b. The bridge circuitscan be the same as the bridge circuits 1710, as described herein. Themonitoring system 1800 can be configured to monitor operating parametersof industrial equipment.

The monitoring subsystems 1801 a, 1801 b can generally be similar to themonitoring system 1800 described above with regard to FIG. 4 , but eachof the monitoring subsystems 1801 a, 1801 b can include a bridge circuitconfigured to facilitate communication between backplanes of themonitoring subsystems 1801 a, 1801 b. Each monitoring subsystem caninclude any number of functional circuits 310 a, 310 b and bridgecircuits that can be detachably coupled to backplanes 306 a, 306 b viaports 308 a, 308 b of the backplanes 306 a, 306 b. The functionalcircuits 310 a, 310 b can be the same as the functional circuits 310.

The backplanes 306 a, 306 b can be, include, or form part of, a physicalbus. The backplanes 306 a, 306 b can be passive backplanes 306 a, 306 bthat can be configured to facilitate multipoint asynchronous electroniccommunication between the functional circuits 310 a, 310 b and/or bridgecircuits 1710 a, 1710 b that are coupled to the backplanes 306 a, 306 b.Therefore, all data that is delivered to the backplanes 306 a, 306 b canbe received by all functional circuits 310 a, 310 b and/or bridgecircuits 1710 coupled to the backplanes. The backplane 306 a can includedata lanes 1812 a, 1812 b, 1812 c, 1812 d -1812 n, and the backplane 306b can include data lanes 1812 a, 1813 b, 1813 c, 1813 d -1813 n, asshown in FIG. 21 . Referring to FIGS. 20-21 , the data lanes 1812 a-1812 n, 1813 a -1813 n are in electronic communication with a number ofports 308 a, 308 b on the respective backplanes 306 a, 306 b. The ports308 a, 308 b can be configured to receive functional circuits 310 a, 310b and/or bridge circuits 1710 a, 1710 b. Each port 308 a, 308 b isconfigured to enable electronic communication between a functionalcircuit 310 a, 310 b or bridge circuit 1710 a, 1710 b coupled to theport, and all of the data lanes 1812 a -1812 n, 1813 a of the respectivebackplanes 306 a, 306 b.

There are a number of different types of functional circuits that can becoupled to ports of the backplanes 306 a, 306 b. For example, one ormore of the functional circuits can be an input circuit (e.g., inputcircuit 210 i), an output circuit (e.g., output circuit 210 o), aprocessing circuit (e.g., processing circuit 210 p), and/or aninfrastructure circuit (e.g., infrastructure circuit 210 n). As shown inthe illustrated example, each functional circuit 310 a, 310 b caninclude a circuit controller 320 a, 320 b and a node 322 a, 322 bconfigured to facilitate and control electronic communication betweenthe circuit controller 320 a, 320 b and the backplane 306 a, 306 b. Asdescribed herein, the node 322 a, 322 b can control delivery of datafrom the circuit controller 320 a, 320 b to the data lanes 312 a, 312 bof the backplane 306 a, 306 b. The nodes 322 a, 322 b can also controlwhich data is delivered from the data lanes 312 a, 312 b to the circuitcontrollers 320 a, 320 b of the functional circuits 310 a, 310 b .

As shown in the illustrated example, the bridge circuits 1710 a, 1710 bcan be detachably coupled to ports 308 a, 308 b of the backplanes 306 a,306 b. The bridge circuits 1710 a, 1710 b can be electrically coupledvia a coupling element 1807 that can between the bridge circuits 1710 a,1710 b. Ends of the coupling element 1807 can be attached to rangeextending elements 1705 a, 1705 b of the bridge circuits 1710 a, 1710 b.The coupling element 1807 can be e.g., electrical cabling and/or fiberoptic cabling. In some embodiments, the bridge circuits 1710 a, 1710 bcan communicate wirelessly. For example, the bridge circuits can includetransceivers for communicating via Bluetooth protocol, cellularprotocol, WI-FI protocol, near field communication (NFC), and/or a radiofrequency identification (RFID) protocol.

In the illustrated example, the bridge circuits 1710 a, 1710 b caninclude bridge controllers 1703 a, 1703 b that are in electroniccommunication with the range extending elements 1705 a, 1705 b and nodes322 a, 322 b of corresponding bridge circuits 1710 a, 1710 b. The nodes322 a, 322 b of the bridge circuits 1710 a, 1710 b can generally besimilar to the nodes 322 of functional circuits 310, as described abovewith regard to FIG. 4 . The nodes 322 a, 322 b can be configured tofacilitate and control electronic communication between the bridgecontrollers 1703 a, 1703 b and the backplanes 306 a, 306 b. For example,the nodes 322 a, 322 b can control delivery of data from the bridgecontrollers 1703 a, 1703 b to the data lanes 1812 a-1812 n, 1813 a-1813n of the backplanes 306 a, 306 b. The nodes 322 a, 322 b can includeschedule controllers 334 a, 334 b, node controllers 324 a 324 b, gatecontrollers 326 a, 326 b, and gate pairs 328 a, 328 b.

As mentioned above, the bridge circuits 1710 a, 1710 b can be configuredto facilitate electronic communication between backplanes 306 a, 306 bof monitoring subsystems. For example, the bridge circuit 1710 a can beconfigured to receive all data delivered to the data lanes 1812 a-1812 nof the backplane 306 a, and provide the data to the bridge circuit 1710b. The bridge circuit 1710 b can receive the data, and can distributethe among data lanes 1813 a-1813 n of the backplane 306 b thatcorrespond to the data lanes 1812 a-1812 n backplane 306 a. For example,all data that is provided from functional circuits 310 a to data lanes1812 a, 1812 b, 1812 c, can be provided to corresponding data lanes 1813a, 1813 b, 1813 c via the bridge circuits 1710 a, 1710 b. Therefore, thebackplanes 306 a, 306 b form an extended logical bus, and the functionalcircuits 310 a, 310 b can function as if they were coupled to a singlebackplane.

As described herein, communication from functional circuits and/orbridge circuits is controlled using a schedule that can be generated bya master circuit. Since all data packets are shared between thebackplanes 306 a, 306 b, the bridge circuits 1710 a, 1710 b and thefunctional circuits 310 a, 310 b can share a schedule. The schedule canbe generated using a single master circuit, which can be one of thefunctional circuits 310 a, 310 b coupled to either of the backplanes 306a, 306 b. The master circuit can generally function to generate anddistribute the schedule, and monitor communication across the data lanes1812 a-1812 n, 1813 a-1813 n, as described herein with regard to FIGS.7-18 .

FIG. 22 shows a data flow diagram 1900 illustrating communicationbetween various components of the monitoring system 1800 during anarbitration period (e.g., arbitration period 411). As an example, themaster circuit can be one of the functional circuits 310 a that iscoupled to the backplane 306 a. At step 1902, the master circuit candeliver a beacon packet that includes a schedule for a current timeframe to data lanes 1812 a-1812 n of the backplane 306 a.

At step 1904, functional circuits 310 a coupled to the backplane 306 acan receive the beacon packet from the backplane 306 a. At step 1906,the node controller 324 a of the bridge circuit 1710 a can receive thebeacon packet and store a copy of the schedule in memory. The nodecontroller 324 a can provide the schedule and/or instructions with theassigned time slices for the current frame to the gate controller 326 a.The gate controller 326 a can use the schedule and/or instructions tocontrol operation of the transmitters 330 a and receivers 332 a, asdescribed in more detail below. The node controller 324 a can alsoprovide the beacon packet to the bridge controller 1703 a. The bridgecontroller 1703 a can receive the beacon packet and provide the beaconpacket to the range extending element 1705 a which can amplify thesignal the beacon packet.

At step 1908 the bridge circuit 1710 a can deliver the beacon packet tothe bridge circuit 1710 a. The range extending element 1705 b of thebridge circuit 1710 b can receive the beacon packet and provide thebeacon packet to the node controller 324 b, which can store a copy ofthe schedule in memory

At step 1910, the node controller 324 b can provide the beacon packet tothe data lanes 1813 a-1813 n of the backplane 306 b via the gatecontroller 326 b and the transmitters of the gate pair 328 b. At step1912, the functional circuits 310 b can receive the beacon packet fromthe backplane 306 b. Node controllers 324 b of the functional circuits310 b can store a copy of the schedule corresponding to the currentframe as well as check the schedule to determine if their previouscommunication requests were schedule. The node controllers 324 b canalso provide the schedule and/or instructions with the assigned timeslices to the gate controllers 326 b. The gate controllers 326 b can usethe schedule and/or instructions to control operation of thetransmitters 330 b and receivers 332 b, as described in more detailbelow.

At step 1914, the functional circuits can provide beacon responsepackets to the data lanes 1813 a-1813 b. At step 1916, the bridgecontroller 1703 b of the bridge circuit 1710 b can receive the beaconresponse packets from each of the data lanes 1813 a-1813 n via thereceivers 332 b, gate controller 326 b, and node controller 324 b. Sincethe data lanes 1813 a-1813 n are in parallel, the bridge controller 1703b receives a parallel data stream that includes, or characterizes, thebeacon response packets. The bridge controller 1703 b can convert, orcondense, the parallel data stream into a serial data stream, andprovide the serial data stream to the range extending element 1705 b.The range extending element can amplify power (e.g., voltage and/orcurrent) of the serial data stream.

At step 1918, the bridge circuit 1710 b provide the serial data streamto the bridge circuit 1710 a via the range extending element 1705 b. Therange extending element 1705 a can receive the serial data stream,attenuate power (e.g., voltage and/or current) of the serial data streamand provide the serial data stream to the bridge controller 1703 a. Thebridge controller 1703 a can receive the serial data stream, expand theserial data stream into parallel data streams.

At step 1920, the bridge controller 1703 a can provide the parallel datastreams to the data lanes 1812 a-1812 n of the backplane 306 a via thenode 322 a. At step 1922, functional circuits 310 a can deliver beaconresponse packets to the data lanes 1812 a-1812 n of the backplane 306 a.At step 1924, the master circuit can receive the beacon response packetsfrom the functional circuits 310 a, 310 b, and generate a schedule forthe following frame.

During normal operation (e.g., during time slices 410C-410N), functionalcircuits 310 a, 310 b can communicate via data lanes 1812 a-1812 n, 1813a-1813 n of the backplanes 306 a, 306 b. For example, functionalcircuits 310 a, 310 b can deliver data packets to the data lanes 1812a-1812 n of the backplane 306 a. The bridge controller 1703 a of thebridge circuit 1710 a can receive the data packets in a parallel datastream, convert, or condense, the parallel data stream into a serialdata stream, and provide the serial data stream to the range extendingelement 1705 a. The range extending element 1705 a can amplify power(e.g., voltage and/or current) of the serial data stream and provide theserial data stream to the bridge circuit 1710 b. The range extendingelement 1705 b can receive the serial data stream, attenuate power(e.g., voltage and/or current) of the serial data stream and provide theserial data stream to the bridge controller 1703 b. The bridgecontroller 1703 b can receive the serial data stream, expand the serialdata stream into parallel data streams, and provide the parallel datastreams to the data lanes 1813 a-1813 n via the node 322 b.

Similarly, functional circuits 310 b can deliver data packets to thedata lanes 1813 a-1813 n of the backplane 306 a. The bridge controller1703 b of the bridge circuit 1710 b can receive the data packets in aparallel data stream, convert, or condense, the parallel data streaminto a serial data stream, and provide the serial data stream to therange extending element 1705 b. The range extending element 1705 b canamplify power (e.g., voltage and/or current) of the serial data streamand provide the serial data stream to the bridge circuit 1710 a. Therange extending element 1705 a can receive the serial data stream,attenuate power (e.g., voltage and/or current) of the serial data streamand provide the serial data stream to the bridge controller 1703 a. Thebridge controller 1703 a can receive the serial data stream, expand theserial data stream into parallel data streams, and provide the paralleldata streams to the data lanes 1812 a-1812 n via the node 322 a. Duringoperation the bridge circuits 1710 a, 1710 b are transparent to all thefunctional circuits 310 a 310 b coupled to the backplanes 306 a, 306 bof the monitoring system. Therefore, the monitoring system 1800functions it appears that the signals/data are all from the same base.

As mentioned above, the gate controllers 326 a, 326 b of the bridgecircuits 1710 a, 1710 b can use the schedule and/or instructions tocontrol operation of the transmitters 330 a, 330 b and receivers 332 a,332 b. For example, the gate controller 326 b can set the transmitters330 b to operate in the first operating mode during time slices when thefunctional circuits 310 a attached to the backplane 306 a are scheduledto deliver data to the backplane 306 a such that the data can bedelivered to the backplane 306 b via the bridge circuits 1710 a, 1710 b.The gate controller 326 b of the bridge circuit 1710 b can set thetransmitters 330 b to operate in the second operating mode during timeslices in which the functional circuits 310 a are not schedule todeliver data to the backplane 306 a. Similarly, the gate controller 326a of the bridge circuit 1710 a can set the transmitters 330 a to operatein the first operating mode during time slices when the functionalcircuits 310 b attached to the backplane 306 b are scheduled to deliverdata to the backplane 306 a such that the data can be delivered to thebackplane 306 a via the bridge circuits 1710 a, 1710 b. The gatecontroller 326 a can set the transmitters 330 a of the bridge circuit1710 a to operate in the second operating mode during time slices whenthe functional circuits 310 b are not schedule to deliver data to thebackplane 306 b.

In some embodiments, separation distances between the bridge circuits1710 a, 1710 b can introduce non-negligible propagation delays intransmissions of data packets between the bridge circuits 1710 a, 1710b. The propagation delays can create time synchronization errors betweenfunctional circuits 310 a, 310 b of each monitoring subsystem 1801 a,1801 b. For example, when the master circuit (e.g., one of thefunctional circuits 310 a) sends the beacon packet, functional circuits310 a that are coupled to the backplane 306 a can receive the beaconpacket before functional circuits 310 b that are coupled to thebackplane 306 b. Therefore, the time synchronization of functionalcircuits 310 b can be delayed as compared to the time synchronization ofthe functional circuits 310 a. Additionally, in some cases, propagationdelays can result in data packet transmissions that extend over multipletime slices, which can result in collisions. For example, if a datapacket is transmitted from a functional circuit 310 b coupled to thebackplane 306 b requires more time to travel to the backplane 306 a thanis allotted in a usable time slice period (e.g., usable time sliceperiod 420), the data packet may still be in transit during a subsequenttime slice. In that case, the data packet may collide with another datapacket that is transmitted during the subsequent time slice.

Dead band periods (e.g., dead band period 424) can be built into timeslices to absorb delays in communication between functional circuitscoupled to a single backplane as well as delays in communication thatresult from bridge backplanes. The dead band periods can function tomitigate data transmission timing errors due to inaccuracies in timesynchronization between functional circuits, as well as minimize signalcollisions that can result from latencies associated with datatransmission between bridged backplanes.

In order to ensure that the time slices include a sufficiently largedead band period, the bridge controllers 1703 a, 1703 b and/or nodecontrollers 324 a, 324 b of the bridge circuits 1710 a, 1710 b canestimate delay times that can characterize an estimated amount of timerequired to transfer data packets between the bridge circuits 1710 a,1710 b. The bridge circuits 1710 a, 1710 b can then determine, identify,or calculate a current allotted dead band period based on informationavailable in the schedule. The bridge circuits 1710 a, 1710 b cancompare the estimated delay times with the allotted dead band period. Insome embodiments, if the dead band period is insufficient, the bridgecircuits 1710 a, 1710 b can deliver data packets to the master circuitto request adjustment of the dead band periods and/or adjustment ofsizes of time slices in subsequent frames.

In some embodiments, when the monitoring subsystems 1801 a, 1801 b arepowered on, the bridge circuits 1710 a, 1710 b can be configured preventdata transmission between the backplanes 306 a, 306 b until hardware andoperating parameters (e.g., communication schedules, baud rates, etc.)of monitoring subsystems (e.g. monitoring subsystems 1801 a, 1801 b) aredetermined to be compatible. For example, the bridge circuits 1710 a,1710 b can be configured to receive data from the backplanes 306 a, 306b, but can be prevented from delivering data to the backplanes 306 a,306 b. In some embodiments, the transmitters 330 a, 330 b can be set tothe second operating mode such that they prevent data from beingdelivered to the data lanes 1812 a-1812 n, 1813 a-1813 n. In someembodiments, the bridge circuits 1710 a, 1710 b can determine ifhardware of the monitoring subsystem is compatible. The bridge circuits1710 a, 1710 b can also determine if any preexisting schedules of themonitoring subsystems 1801 a, 1801 b are compatible. As an example,operating parameters can include schedules, baud rates, etc.

Upon startup, the bridge circuits 1710 a, 1710 b can determine if theyinclude system data stored in memory of the node controllers 324 a, 324b and/or the bridge controllers 1703 a, 1703 b. As an example, systemdata can be, or can include, unique IDs (e.g., MAC addresses)corresponding to components of the monitoring subsystems, informationdescribing how many data lanes each backplane includes, network IDs,etc. FIG. 23 shows a flow chart 2000 illustrating an exemplary method ofdetermining that hardware and operating parameters of monitoringsubsystems (e.g. monitoring subsystems 1801 a, 1801 b) are compatible.

At step 2002, the method can include receiving a first identificationdata at a first bridge circuit (e.g., bridge circuit 1710 a) coupled toa first backplane (e.g., backplane 306 a) of a first monitoringsubsystem (e.g., monitoring subsystem 1801 a). The first identificationdata can characterize information identifying hardware of a secondmonitoring subsystem (e.g., monitoring subsystem 1801 b). As an example,the first identification data can be, or can include, a unique ID (e.g.,a MAC address) of the second backplane (e.g., backplane 306 b) and/orfunctional circuits 310 b coupled thereto. As another example, the firstidentification data can be, or can include, data describing the numberof data lanes that the second backplane includes, as well as a networkID corresponding to the second monitoring subsystem. In someembodiments, the first bridge circuit can receive unique IDs of thefunctional circuits from data packets delivered to the first backplanefrom the second monitoring subsystem during operation. As anotherexample, the first bridge controller can receive data describing thenumber of data lanes from beacon packets (e.g., number of lanes field507). The bridge controller and/or a node controller (e.g., bridgecontroller 1703 a and node controller 324 a) of the first bridge circuitcan store the first identification data in memory during operation. Thefirst identification data can remain in memory during a system shutdown,and can be used to confirm that the first monitoring subsystem and thesecond monitoring subsystem are during a subsequent system startup, asdescribed herein.

At step 2004, the method can include receiving a second identificationdata at a second bridge circuit (e.g., bridge circuit 1710 b) coupled toa second backplane (e.g., backplane 306 b) of the second monitoringsubsystem. The second identification data can characterize informationidentifying hardware of the first monitoring subsystem. As an example,the second identification data can be, or can include, a unique ID(e.g., a MAC address) of the first backplane and/or functional circuitscoupled thereto. As another example, the second identification data canbe, or can include, data describing the number of data lanes that thefirst backplane includes, as well as a network ID corresponding thefirst monitoring subsystem. In some embodiments, the second bridgecircuit can receive unique IDs of the functional circuits from beaconpackets or other data packets delivered to the second backplane from thefirst monitoring subsystem during operation. As another example, thesecond bridge controller can receive data describing the number of datalanes from beacon packets (e.g., number of lanes field 507). The bridgecontroller and/or a node controller (e.g., node controller 324 b andbridge controller 1703 b) of the second bridge circuit can store thesecond identification data in memory during operation. The secondidentification data can remain in memory during a system shutdown, andcan be used to confirm that the first monitoring subsystem and thesecond monitoring subsystem are compatible during a subsequent systemstartup, as described herein.

In some embodiments, the second identification data can be stored inmemory of the node controller and/or bridge controller of the firstbridge circuit, and the first bridge circuit can provide the secondidentification data to the second bridge circuit. Similarly, the firstidentification data can be stored in memory of the node controllerand/or bridge controller of the second bridge circuit, and the secondbridge circuit can provide the first identification data to the firstbridge circuit. As another example, the first and second identificationdata can be stored in memory of node controllers and/or bridgecontrollers of the first and second bridge circuits.

At step 2006, the first identification data and the secondidentification data can be used to determine that the first monitoringsubsystem is compatible with the second monitoring subsystem. Forexample, the bridge controllers and/or node controllers of the first andsecond bridge circuits can confirm that the first backplane and thesecond backplane have the same number of data lanes. As another example,bridge controllers and/or node controller of can use the unique IDs offunctional circuits and/or backplanes of the first and second monitoringsubsystems to determine that the first and second monitoring subsystemsare compatible. The bridge controllers and/or node controllers can alsocompare network IDs provided with the first and second identificationdata to determine that the first and second monitoring systems arecompatible. For example, if the network IDs are the same, the monitoringsystem can be determined to be compatible.

At step 2008, the method can include receiving a first schedule at thesecond bridge circuit. The first schedule can characterize a firstcommunication schedule for a first set of functional circuits that arein electronic communication with the first backplane. In someembodiments, the first schedule can be stored in memory of the nodecontroller and/or bridge controller of the first bridge circuit, and thefirst bridge circuit can provide the first schedule to the second bridgecircuit. As another example, the bridge controller and/or a nodecontroller of the second bridge circuit receive the first schedule in abeacon packet during operation. The bridge controller and/or a nodecontroller of the second bridge circuit can store the first schedule inmemory. The first schedule can remain in memory during a systemshutdown, and can be available for use in a subsequent system startup,as described herein.

At step 2010, the method can include receiving a second schedule at thefirst bridge circuit. The second schedule can characterize a secondcommunication schedule for a second set of functional circuits that arein electronic communication with the second backplane. In someembodiments, the second schedule can be stored in memory of the nodecontroller and/or bridge controller of the second bridge circuit, andthe second bridge circuit can provide the second schedule to the firstbridge circuit. As another example, the bridge controller and/or a nodecontroller of the first bridge circuit receive the second schedule in abeacon packet during operation. The bridge controller and/or a nodecontroller of the first bridge circuit and can store the second schedulein memory. The first schedule can remain in memory during a systemshutdown, and can be available for use in a subsequent system startup,as described herein.

The first communication schedule can be compared to the secondcommunication schedule at step 2012. For example, the first and secondbridge circuits can compare the first and second schedule to ensure thatfunctional circuits of the first monitoring subsystem are not scheduledto deliver data to data lanes of the first backplane at the same timethat functional circuits of the second monitoring subsystem are scheduleto deliver data to corresponding data lanes of the second backplane.

At step 2014, the method can include determining that the first scheduleis compatible with the second schedule. For example, if the comparisonindicates that functional circuits of the first monitoring subsystem arenot scheduled to deliver data to data lanes of the first backplane atthe same time that functional circuits of the second monitoringsubsystem are schedule to deliver data to corresponding data lanes ofthe second backplane, the first and second bridge circuits can determinethat the first and second schedule are compatible.

At step 2016, the method can include providing a first signal to atleast one first gate (e.g., transmitter 330 a) of the first bridgecircuit and providing a second signal to at least one second gate (e.g.,the transmitter 330 b) of the second bridge circuit, thereby activatingthe at least one first gate and the at least one second gate, andfacilitating electronic communication between the first backplane andthe second backplane. As an example, node controllers of the first andsecond bridge circuits can provide data to the gate controllers of thefirst and second bridge circuit to confirm that the schedules of thefirst and second monitoring subsystem are compatible. The gatecontrollers can activate gates (e.g., transmitters 330 a, 330 b) of thefirst and second bridge circuits by delivering signals to the gates toset the gates to operate in the first operating mode, thereby allowingdata to be transmitted from the bridge circuits, and allowing data to betransferred between the first and second monitoring subsystems.

In some embodiments, network IDs of the first and second monitoringsubsystems can be used to determine of the first and second monitoringsubsystems are compatible. The network IDs can also be used to determineif the first and second schedules are compatible.

As an example, the first bridge circuit can provide the second bridgecircuit with a first network ID that characterizes a configuration ofthe first monitoring subsystem. The second bridge circuit can providethe first bridge circuit with a second network ID that characterizes aconfiguration of the second monitoring subsystem. The first and secondnetwork IDs can include data such as, e.g., unique IDs of functionalcircuits and/or the backplane, number of data lanes on the backplane,etc. corresponds to hardware of the first and second monitoringsubsystems as well as operating parameters such as e.g., communicationschedules, the baud rate, etc. of the first and second monitoringsubsystems. The bridge controllers and/or node controllers of the firstand second bridge circuits can compare the first network ID with thesecond network ID to determine if the hardware and operating parametersof the first and second monitoring subsystems are compatible. If thenetwork IDs indicate that the hardware and operating parameters of thefirst and second monitoring subsystem are compatible, node controllersof the first and second bridge circuits can provide data to the gatecontrollers of the first and second bridge circuit to confirm thecompatibility of the first and second monitoring subsystems. The gatecontrollers can activate gates (e.g., transmitters 330 a, 330 b) of thefirst and second bridge circuits by delivering signals to the gates toset the gates to operate in the first operating mode, thereby allowingdata to be transmitted from the bridge circuits, and allowing data to betransferred between the first and second monitoring subsystems.

After the gates first and second bridge circuit are set to operate inthe first operating mode, functional circuits of the first and secondmonitoring subsystem can then execute an initialization process toselect a master node, as described above with regard to FIG. 13 . Themaster circuit can generate and distribute a third schedule, and monitordata delivered to the backplanes, as described above with regard toFIGS. 14-17 .

In some embodiments, when the monitoring subsystems are powered, thefirst and second bridge circuits may not have access to preexisting data(e.g., identification data, network IDs, schedules, etc.) that can beused to determine if hardware and operating parameters of the first andsecond subsystems are compatible. In that case, the first and secondbridge circuits can used data from beacon packets to determine ifhardware and operating parameters of the first and second subsystems arecompatible.

Initially, upon system startup one or more functional circuits coupledto each of the first and second backplanes (e.g., backplanes 306 a, 306b) can begin an initialization process to assume arbitrationresponsibilities and become a master circuit, as described above withrespect to FIG. 13 . At the end of the initialization processes, thefirst monitoring subsystem (e.g., monitoring subsystem 1801 a) caninclude a first master circuit, and the second monitoring subsystem(e.g., monitoring subsystem 1801 b) can include a second master circuit.

The first and second master circuits can deliver first and second beaconpackets to data lanes of the first and second backplanes, respectively.The beacon packets can generally be similar to the beacon packet 500,describe with regard to FIG. 8 . Each beacon packet can include apreamble, type, current time, number of lanes, baud rate, scheduleheader, and schedule entries fields.

The bridge controller (e.g., bridge controller 1703 a) of the firstbridge circuit can receive the first beacon packet, and the bridgecontroller (e.g., bridge controller 1703 b) of the second bridge circuitcan receive the second beacon packet. The bridge controller and/or nodecontroller of the first bridge circuit can store data corresponding tothe fields of the first beacon packet in memory. The bridge controllerand/or node controller of the second bridge circuit can store datacorresponding to the fields of the second beacon packet in memory.

The bridge controller of the first bridge circuit can deliver the firstbeacon packet to a range extending element (e.g., range extendingelement 1705 a) of the first bridge circuit. The range extending elementcan amplify power (e.g., voltage and/or current) of a signalcorresponding to the first beacon packet, and can provide the firstbeacon packet to the bridge controller and/or node controller of thesecond bridge circuit. The bridge controller of the second bridgecircuit can deliver the second beacon packet to a range extendingelement (e.g., range extending element 1705 b) of the second bridgecircuit. The range extending element can amplify power (e.g., voltageand/or current) of a signal corresponding to the second beacon packet,and can provide the second beacon packet to the bridge controller and/ornode controller of the first bridge circuit.

The bridge controllers and/or note controllers of the first and secondbridge circuits can compare the data corresponding to the fields (e.g.,preamble, type, current time, number of lanes, baud rate, scheduleheader, and schedule entries fields) provided within the first andsecond beacon packets to determine if the first and second monitoringsubsystems are compatible.

If the first and second monitoring subsystems are determined to becompatible, node controllers of the first and second bridge circuits canprovide data to the gate controllers of the first and second bridgecircuit to confirm that the first and second monitoring subsystems arecompatible. The gate controllers can activate gates (e.g., transmitters)of the first and second bridge circuits by delivering signals to thegates to set the gates to operate in the first operating mode, therebyallowing data to be transmitted from the bridge circuits, and allowingdata to be transferred between the first and second monitoringsubsystems.

After the monitoring subsystems are in electronic communication, one ofthe master circuits can relinquish arbitration capabilities such thatonly one master circuit is shared between the first and secondbackplane. For example, if one of the master circuits detects a beaconpacket, the master circuit can enter a state of random back-off, asdescribed above with regard to step 1112, shown in FIG. 13 . In someembodiments, the former master circuit can remain in a state of randomback-off and function as a slave note until it does not receive a beaconpacket during a beacon time slice (e.g., beacon time slice 410A). If theformer master circuit does not receive a beacon packet during beacontime slice, the former master circuit can assume arbitrationresponsibilities, thereby becoming the master circuit, as described withregard to step 1114, shown in FIG. 13 .

Bridge circuits can function to electrically couple backplanes to forman extended logical bus such that all data is transferred between thebackplanes. This allows monitoring systems to span between multiplelocations while retaining the full functionality that is available whenusing monitoring systems that include a single backplane. Additionally,since all data is shared between bridged backplanes, the bridges allowfor resources (e.g., functional circuits) to be distributed between thebackplanes as desired.

FIG. 24 shows block diagram of another exemplary monitoring system 2100.As shown in the illustrated example, the monitoring system includemonitoring subsystems 2101 a, 2101 b that can be electrically coupledusing bridge circuits 1710 a, 1710 b. Coupling elements 1807 canelectrically couple the bridge circuits 1710 a, 1710 b. The first andsecond monitoring subsystems 2101 a, 2101 b can include backplanes 2106a, 2106 b that can generally be similar to the backplane 306 a, 306 b.

The monitoring subsystems 2101 a, 2101 b can include various differentfunctional circuits that can be coupled to ports of the backplanes 2106a, 2106 b. The backplanes 2106 a, 2106 b can be, include, or form partof, a physical bus. The backplanes 2106 a, 2106 b can generally besimilar to the backplanes 306 a, 306 b described above with regard toFIGS. 4, 20 .

The first monitoring subsystem 2101 a include condition monitoringcircuits 2102 a, gateway circuits 2104 a, system interface circuits 2108a, power input circuits 2110 a, a discrete input circuit 2112 a,protection circuits 2114 a, 4-20 output circuits 2116 a, relay circuits2118 a, and bridge circuits 1710 a. The second monitoring subsystem 2101b can include dynamic input circuits 2120 b, static input circuits 2122b, relay circuits 2118 b, and PIM circuits 2110 b.. As shown in theillustrated example, the monitoring subsystems 2101 a, 2101 b can becoupled via multiple bridge circuits 1710 a, 1710 b for the purpose ofredundancy. If one of the bridge circuits fails, another pair of bridgecircuits is available to bridge communications between the backplanes2106 a, 2106 b.

As shown in the illustrated example, the monitoring subsystem 2101 b canprimarily function receive analog sensor data, digitize the sensor data,and provide data packets corresponding to the sensor data to data lanesof the backplane 2106 b using the various input circuits. The monitoringsubsystem 2101 a can primarily function to provide updates to themonitoring system (e.g., via the system interface circuit 2108 a),process the sensor data (e.g., using the protection circuits 2114 a),and provide processed data to users (e.g., via the gateway circuit 2104a, condition monitoring circuit 2102 a).

Bridging can allow for monitoring subsystem to share common resources(e.g., functional circuits), which can provide flexibility whendesigning and installing monitoring systems. For example, the monitoringsubsystem 2101 b can be installed remotely near industrial equipmentsuch that the input circuits can receive sensor data, while themonitoring subsystem 2101 a can be installed at another location thatmay be more convenient, or easier to access. Installing the monitoringsubsystem near the industrial equipment to be monitored, can also reducecosts of running cables from the sensors to the input circuits, as wellas improve the quality of the signals delivered from sensors to theinput circuits by reducing exposure to noise and ground loops. As anexample, ground loops be described as interference resulting fromportions of a circuit that are at different ground reference voltages,rather than the same ground reference voltage. Ground loops can causeundesirable signal degradation and/or noise within signals. Themonitoring subsystem 2101 b can take advantage of resources (e.g.,condition monitoring circuits 2102 a, gateway circuits 2104 a, systeminterface circuits 2108 a, PIM circuits 2110 a, a discrete input circuit2112 a, protection circuits 2114 a, 4-20 output circuits 2116 a, relaycircuits 2118 a,) installed on the monitoring subsystem 2101 a.

FIG. 25 shows block diagram of another exemplary monitoring system 2200.As shown in the illustrated example, the monitoring system 2200 includemonitoring subsystems 2201 a, 2201 b, 2201 c that can be electricallycoupled via bridge circuits 1701 a, 1701 b, 1701 c. The monitoringsubsystems 2201 a, 2201 b, 2201 c can include backplanes 2206 a, 2206 b,2206 c that can be coupled via the bridge circuits 1701 a, 1701 b, 1701c. The backplanes 2206 a, 2206 b, 2206 c can generally be similar to thebackplanes 2106 a, 2106 b. The coupled backplanes 2206 a, 2206 b, 2206 cform an extended logical bus.

The monitoring subsystems 2201 a, 2201 b, 2201 c can include variousmonitoring circuits that can be coupled to the respective backplanes.The monitoring subsystem 2201 a can include a condition monitoringcircuit 2102 a, a gateway circuit 2104 a, a system interface circuit2108 a, a discrete input circuit 2112 a, a relay circuit 2118 a, PIMcircuits 2110 a, and bridge circuits 1710 a. The monitoring subsystem2201 b can include a protection circuit 2114 b, dynamic input circuits2120 b, 4-20 output circuits 2116 b, relay circuits 2118 b, power inputcircuits 2110 b, and bridge circuits 1710 b. The monitoring subsystem2201 c can include dynamic input circuits 2120 c, a PIM circuit 2110 c,a relay circuit 2118 c, and bridge circuits 1710 c.

In some embodiments, the monitoring subsystem 2201 b can function as theprimary monitoring subsystem. For example, the monitoring subsystem 2201b can be positioned locally near a critical piece of industrialequipment. The 4-20 output circuits 2116 b can be configured to outputanalog sensor data, which can allow local users to troubleshootoperation of the dynamic input circuits and/or sensors coupled to thedynamic input circuits of the monitoring subsystem 2201 b to ensure thatthe monitoring subsystem 2201 b is functioning properly. In someembodiments, the monitoring subsystems 2201 c can be installed remotelynear another industrial system. The monitoring subsystem 2201 a canprimarily function to provide updates to the monitoring system (e.g.,via the system interface circuit 2108 a), and provide processed data tousers (e.g., via the gateway circuit 2104 a, and the conditionmonitoring circuit 2102 a). For example, the gateway circuit 2104 a canfunction to provide data to, and receive data from, trusted users (e.g.,plant operators). The condition monitoring circuit, which cannot deliverdata packets to the backplane 2206 a, can function to provide untrustedusers (e.g., remote technical support operators) with datacharacterizing operation of the industrial system.

Bridging can allow for monitoring subsystem to share common resources,which can provide flexibility when designing and installing monitoringsystems. For example, monitoring subsystems (e.g., monitoring subsystem2201 c) can be installed remotely near industrial equipment such thatthe input circuits can receive sensor data, while other monitoringsubsystems (e.g., monitoring subsystem 2201 b) can be installed atanother location that may be more convenient, or easier to access, orhave a system that is more critical to monitor. Installing monitoringsubsystems near the industrial equipment to be monitored, can alsoreduce costs of running cables from the sensors to input circuits, aswell as improve the quality of the signals delivered from sensors to theinput circuits by reducing exposure to noise and ground loops. . Sincemonitoring system can share common resources, bridging can also allowmonitoring systems to be expanded more cost effectively. For example,monitoring subsystems (e.g., monitoring subsystem XC) can be added tomonitoring systems to monitor operation of industrial equipment thatmight not be critical, or might otherwise be cost prohibitive tomonitor.

In some embodiments, rather than using passive backplanes (e.g.,backplanes 306 a, 306 b 2106 a, 2106 b, etc.) to facilitatecommunication between functional circuits of a monitoring system,Ethernet networks can be used to facilitate communication betweenfunctional circuits. In some embodiments, Ethernet protocols such as,e.g., TCP/IP and/or TSN can be used to facilitate and controlcommunication between functional circuits.

FIG. 26 shows a block diagram of an exemplary monitoring system 2300that utilizes the TSN Ethernet protocol to facilitate communicationbetween functional circuits of the monitoring system 2300. As shown inthe illustrated example, the monitoring system 2300 includes a sensorinput subsystem 2302, a marshalling cabinet 2304, and an instrumentcabinet 2306. The sensor input subsystem 2302 can be configured toreceive signals from sensors 2308 configured to measure operatingparameters of an industrial system 2310, and provide digital signalscharacterizing the sensor measurements to the marshalling cabinet 2304.The marshalling cabinet 2304 can be configured provide alarm/alerts to acontrol system (e.g., customer control system 212), and to facilitatecommunication between the instrument cabinet 2306 and the sensor inputsubsystem 2302. The instrument cabinet 2306 can be configured to processsensor data, receive and distribute updates to the monitoring system2300, and provide users with data characterizing operation of theindustrial system 2310.

As shown in FIG. 26 , the sensor input subsystem 2302 can includejunction 2312 boxes that are configured to receive the sensor signals,and a conduit 2314 that can house coupling elements 2316 (e.g., Ethernetcables) that extend between the junction boxes 2312 and to themarshalling cabinet 2304. The junction boxes 2312 can be configured toreceive signals from the sensors, condition the signals, and providedigital signals characterizing the sensor measurements to themarshalling cabinet 2304. In some embodiments, sensors 2308 can beconfigured to provide analog signals, discrete signals, and/or digitalsignal streams.

FIG. 27 shown a detailed view of components within the junction boxes2312. As shown in FIG. 27 , the junction boxes 2312 can include multiplesignal conditioners 2318 that can be in electronic communication withthe sensors 2308 and with input circuits 2320. The junction boxes 2312can also include a power supply 2319 that can be electrically coupled tothe signal conditioners 2318 and to the input circuits 2320. The powersupply 2319 can be configured to power the signal conditioners 2318 andthe input circuits 2320. The signal conditioners 2318 can be configuredto receive signals from the sensors 2308, adjust a voltage and/orcurrent of the signal, and provide the adjusted signal to the inputcircuits 2320.

Depending on the type of signal provided by the sensors 2308 the inputcircuits 2320 can be configured to receive the adjusted signals from thesignal conditioners 2318, convert the signals to digital signals, adjusta voltage and/or current of a discrete signal, adjust a current and/orvoltage of a digital signal stream, and provide adjusted digital signalto the marshalling cabinet 2304 via the coupling elements .

As shown in the illustrated example, the marshalling cabinet can includea relay circuit 2322, power supplies 2324, signal barriers 2326, andcable couplings 2328 a. The power supplies 2324 can be electricallycoupled to the relay circuit 2322. The power supplies 2324 can beconfigured to provide power to the relay circuit 2322 a. The signalbarriers 2326 can function to prevent potentially dangerous signals frombeing transmitted to the sensor input system 2302. For example, if thesensor input subsystem 2302 is positioned within an environment thatcontains combustible gasses, the signal barriers 2326 can be configuredto prevent signals that are beyond a predetermine voltage and/or currentfrom being delivered to the sensor input subsystem 2302. The relaycircuit 2322 a can be electrically coupled to the sensor input subsystem2302 via the coupling elements 2327 a and the signal barrier 2316. Therelay circuit 2322 a can also be electrically coupled to the cablecoupling 2328 a such that it is in electrical communication withfunctional circuits within the instrument cabinet 2306.

The instrument cabinet 2306 can include protection circuits 2330 a, 2330b a relay circuit 2322 b, a 4-20 output circuit 2332, a system interfacecircuit 2334, gateway circuit 2336, and cable couplings 2328 b. Thepower supplies 2324 can also provide power to the protection circuits2330 a, 2330 b, relay circuit 2322 b, 4-20 output circuit 2332, systeminterface circuit 2334, and gateway circuit 2336 within the instrumentcabinet 2306. The protection circuits 2330 a, 2330 b, relay circuit 2322b, 4-20 output circuit 2332, system interface circuit 2334, and gatewaycircuit 2336 can generally function similarly to other protectioncircuits, relay circuit, 4-20 output circuit, system interface circuit,and gateway circuits as described herein. Coupling elements 2327 b canextend from the cable couplings 2328 b to the protection circuit 2330 aand the gateway circuit 2336. Coupling elements 2327 b can also extendbetween the protection circuits 2330 a, 2330 b the relay circuit 2322 b,4-20 output circuit 2332, system interface circuit 2334, and gatewaycircuit 2336, such that the protection circuits 2330 a, 2330 b, relaycircuit 2322 b, 4-20 output circuit 2332, system interface circuit 2334,and gateway circuit 2336 can be electrically coupled between the cablecouplings 2328 b.

The instrument cabinet 2306 can be electrically coupled to themarshalling cabinet 2304 via coupling elements 2338. In someembodiments, the coupling elements 2338 can be fiber optic cabling thatcan extend between cable couplings 2328 a, 2328 b of the marshallingcabinet 2304 and the instrument cabinet 2306. The cable couplings 2328a, 2328 b can be configured to function as an interface between couplingelements 2327 a, 2327 b within the marshalling cabinet 2304 and theinstrument cabinet 2306, and coupling elements 2338 that extend betweenthe marshalling cabinet 2304 and the instrument cabinet 2306.

In operation, the sensor input subsystem 2302 can provide digitalsignals characterizing sensor measurements to the marshalling cabinet2304. The digital signals can travel through the coupling elements 2327within the marshalling cabinet 2304 to the relay circuit 2322. Thedigital signals can also be provided to the instrument cabinet 2306 viathe cable couplings 2328 a, 2328 a, and the coupling elements 2338 thatextend therebetween. Within the instrument cabinet 2306, the digitalsignals can be provided to the protection circuits 2330, the relaycircuit 2322 b, the 4-20 output circuit 2332, the system interfacecircuit 2334, and gateway circuit 2336.

In some embodiments, input circuits can be positioned within amarshalling cabinet of monitoring system that utilizes the TSN Ethernetprotocol to facilitate communication between functional circuits of amonitoring system. FIG. 28 shows a block diagram of another exemplarymonitoring system 2400 that utilizes the TSN Ethernet protocol tofacilitate communication between functional circuits of a monitoringsystem. The monitoring system 2400 can generally be similar to themonitoring system 2300 illustrated in FIG. 26 , but can include inputcircuits positioned within a marshalling cabinet 2404.

As shown in the illustrated example, the monitoring system 2400 includesa sensor input subsystem 2402, a marshalling cabinet 2404, and aninstrument cabinet 2406. The sensor input subsystem 2402 can beconfigured to receive signals from sensors 2308 configured to measureoperating parameters of an industrial system 2310, condition the sensorsignals, and provide conditioned sensor signals characterizing thesensor measurements to the marshalling cabinet 2404. The marshallingcabinet 2404 can be configured receive the conditioned sensor signalsand provide digital signals characterizing the sensor measurements tothe instrument cabinet 2406. The marshalling cabinet 2404 can also beconfigured provide alarm/alerts to a control system (e.g., customercontrol system 212), and to facilitate communication between theinstrument cabinet 2306 and the sensor input subsystem 2302. Theinstrument cabinet 2406 can be configured to process sensor data,receive and distribute updates to the monitoring system 2400, andprovide users with data characterizing operation of the industrialsystem 2310.

The sensor input subsystem 2402 can include junction 2412 boxes that canbe configured to receive the sensor signals, and a conduit 2414 that canhouse coupling elements 2416 (e.g., Ethernet cables) that extend betweenthe junction boxes 2412 and to the marshalling cabinet 2404. Thejunction boxes 2412 can generally be similar to the junction boxes 2312but do not include input circuits. The junction boxes 2412 can beconfigured to receive signals from sensors 2308, condition the sensorsignals, and provide conditioned sensor signals characterizing thesensor measurements to the marshalling cabinet 2404 via the couplingelements 2416. In some embodiments, the coupling elements 2416 can beanalog field wires.

The marshalling cabinet 2404 can include input circuits 2320, powersupplies 2324, a relay circuit 2322, signal barriers 2326, and cablecouplings 2328 a. The power supplies 2324 can be electrically coupled tothe input circuits 2320, the relay circuits 2322 a, and other functionalcircuits within the instrument cabinet 2406. The signal barrier 2326 canbe coupled to the coupling elements 2416. The input circuits 2320 can becoupled to the junction boxes 2412 via a coupling element 2417 thatextends between each of the input circuits 2320 and the signal barrier2326. The input circuits 2320 and the relay circuit 2322 a can be inelectrically coupled via coupling elements 2327 a that extend betweeneach of the input circuits 2320 a, the relay circuit 2322 a, and thecable coupling 2328 a.

The instrument cabinet 2406 can include protection circuits 2330 a, 2330b a relay circuit 2322 b, a 4-20 output circuit 2332, a system interfacecircuit 2334, gateway circuit 2336, and a cable coupling 2328 b. Thepower supplies 2324 can provide power to the protection circuits 2330 a,2330 b, relay circuit 2322 b, 4-20 output circuit 2332, system interfacecircuit 2334, and gateway circuit 2336 within the instrument cabinet2306. Coupling elements 2327 b can extend from the cable coupling 2328 bto the protection circuit 2330 a and the gateway circuit 2336. Couplingelements 2327 b can also extend between the protection circuits 2330 a,2330 b the relay circuit 2322 b, 4-20 output circuit 2332, systeminterface circuit 2334, and gateway circuit 2336, such that theprotection circuits 2330 a, 2330 b, relay circuit 2322 b, 4-20 outputcircuit 2332, system interface circuit 2334, and gateway circuit 2336can be electrically coupled.

The instrument cabinet 2406 can be electrically coupled to themarshalling cabinet 2406 via coupling elements 2438. In someembodiments, the coupling elements 2338 can be fiber optic cabling thatcan extend between cable couplings 2328 a, 2328 b of the marshallingcabinet 2404 and the instrument cabinet 2406. The cable couplings 2328a, 2328 b can be configured to function as an interface between couplingelements 2327 a, 2327 b within the marshalling cabinet 2404 and theinstrument cabinet 2406, and coupling elements 2438 that extend betweenthe marshalling cabinet 2404 and the instrument cabinet 2406.

In operation, the sensor input subsystem 2402 can provide conditionedsignals characterizing sensor measurements to the marshalling cabinet2304. The input circuits 2320 can receive the conditioned signals. Theinput circuits 2320 can generate digital signals based on theconditioned signals, and provide the digital signals to the relaycircuit 2322 a and the he instrument cabinet 2406 via the cablecouplings 2328 a, 2328 a, and the coupling elements 2438 that extendtherebetween. Within the instrument cabinet 2306, the digital signalscan be provided to the protection circuits 2330, the relay circuit 2322b, the 4-20 output circuit 2332, the system interface circuit 2334, andgateway circuit 2336.

Traditional monitoring systems can be limited in terms of flexibilityand scalability. Additionally, costs and complexity of installation cancreate a significant barrier to entry for users that want to monitor lowcost and/or low priority components/systems. By utilizing functionalcircuits that can be detachably coupled to the backplane, performance ofthe monitoring systems described herein can be adjusted and/or scaled tofit individual monitoring needs. For example, processing power can beincreased by coupling additional processing circuits to the backplane.Additionally, utilizing bridge circuits to facilitate communicationbetween multiple backplanes can allow for monitoring subsystem of amonitoring system to share common resources, which can provideflexibility when designing and installing monitoring systems. Forexample, monitoring subsystems (e.g., monitoring subsystem 2101 b) canbe installed remotely near industrial equipment such that the inputcircuits can receive sensor data, while other monitoring subsystems(e.g., monitoring subsystem 2101 a) can be installed at another locationthat may be more convenient, or easier to access. Installing monitoringsubsystems near the industrial equipment to be monitored can also reducecosts of running cables from the sensors to input circuits, as well asimprove the quality of the signals delivered from sensors to the inputcircuits by reducing exposure to noise and ground loops. Sincemonitoring system can share common resources, bridging can also allowmonitoring systems to be expanded more cost effectively. For example,monitoring subsystems (e.g., monitoring subsystem 2201 c) can be addedto monitoring systems to monitor operation of industrial equipment thatmight not be critical, or might otherwise be cost prohibitive tomonitor.

Exemplary technical effects of the subject matter described herein caninclude the ability to bridge multiple backplanes of a monitoring systemto create an extended logical bus. The extended logical bus allowsmonitoring systems to span between multiple locations while retainingthe full functionality that is available when using monitoring systemsthat include a single backplane. Additionally, since all data is sharedbetween bridged backplanes, the bridges allow for resources (e.g.,monitoring circuits) to be distributed between the backplanes asdesired. For example, monitoring subsystems can be installed remotelynear industrial equipment such that the input circuits can receivesensor data, while other monitoring subsystems can be installed atanother location that may be more convenient, or easier to access.Installing monitoring subsystems near the industrial equipment to bemonitored can also reduce costs of running cables from the sensors toinput circuits, as well as improve the quality of the signals deliveredfrom sensors to the input circuits by reducing exposure to noise andground loops.

In some embodiments, a monitoring system can utilize a backplane thathas dedicated data lanes that only receive data from one input circuit.Therefore, if a data lane fails during operation, the impact of thatfailure can be limited to a single monitoring circuit that is configuredto deliver data to that particular data lane. FIG. 29 shows a blockdiagram of a portion of an exemplary embodiment of a monitoring system2500 utilizes dedicated data lanes to facilitate communication betweenmonitoring circuits 2510.

The monitoring system 2500 can include any number of monitoring circuits2510, which can be detachably coupled to a backplane 2506 via ports 2508of the backplane 2506. As shown in the illustrated example, themonitoring system includes input circuits 2550, protection circuits2552, a system interface circuit 2554, a condition monitoring circuit2556, a 4-20 output circuit 2561, a relay circuit 2558, and a gatewaycircuit 2559. In some embodiments the input circuits 2550 can be, e.g.,dynamic input circuits. The backplane can be, include, or form part of,a physical bus. In some embodiments, the backplane can have a unique IDthat can be used to identify the backplane. The backplane can be apassive backplane configured to facilitate multipoint asynchronouselectronic communication between the functional circuits that arecoupled to the backplane. Therefore, all data that is delivered to thebackplane can be received by all functional circuits 2510 that arecoupled to the backplane 2506.

In the illustrated example, the backplane includes a set of input datalanes 2512 a, a set of protection data lanes 2512 b, and at least onesystem data lane 2512 c. The protection data lanes 2512 b and input datalanes 2512 a can be single-direction serial communication lanes. Each ofthe input data lanes 2512 a can be configured to receive data packetsfrom an input circuits 2550 coupled to a port that can be configured tofacilitate data delivery to the corresponding monitoring lane. As shownin the illustrated example, each input data lane 2512 a can receive datapackets from a single input circuit 2550. Each input data lane 2512 acan be in electronic communication with ports 2508 configured to receiveinput circuits 2550, protection circuits 2552, the system interfacecircuit 2554, the condition monitoring circuit 2556, the 4-20 outputcircuit 2561, the relay circuit 2558, and the gateway circuit 2559.

In some embodiments, all of the input, protection, and system data lanes2512 a, 2512 b, 2512 c can be electrically coupled to each of the ports.However, for clarity, unused connections between the ports 2508 and theinput, protection, and system data lanes 2512 a, 2512 b, 2512 c areomitted in FIGS. 29-34 .

The protection data lanes 2512 b can function to provide trustedsystems/users with alarms and/or other data characterizing operation ofthe industrial equipment being monitored. As shown in the illustratedexample, each of the protection data lanes 2512 b can be in electroniccommunication with a port configured to couple to a protection circuitsuch that the protection data lane is configured to receive data packetsfrom the protection circuit. All of the protection data lanes 2512 b canbe in electronic communication with ports configured to receive relaycircuits 2558 such that alarm signals provided by the protectioncircuits can be provided to trusted systems (e.g., customer controlsystem 212).

Each of the input data lanes 2512 a and protection data lanes 2512 b canbe dedicated data lanes, such that each of the input data lanes 2512 aand protection data lanes 2512 b are configured to receive data from oneinput circuit 2550 and one protection circuit 2552, respectively.

The system data lane 2512 c can be a bi-directional serial communicationlane. The system data lane 2512 c can function as a communication lanefor the system interface circuit to perform update operating parameters,operating thresholds, or configurations, of any of the functionalcircuits. The system data lane 2512 c can also allow the systeminterface circuit to adjust, or set, alarm conditions for protectioncircuits as well as conditions for actuation of relay circuits 2558. Thesystem data lane 2512 c can be in electronic communication with all ofthe ports of the backplane, such that functional circuits coupled toeach port can deliver data packets to, and receive data packets from,the system data lane 2512 c. In some embodiments, the system data lane2512 c can be a command/response lane that can be controlled by thesystem interface circuit 2554, as described in more detail below.

Each input circuit 2550 can be in electronic communication with one ofthe input data lanes 2512 a, as well as with the system data lane 2512c. The input circuits 2550 can be configured to receive sensor signals,perform signal conditioning on the sensor signals, and output theconditioned sensor signals to the input data lanes 2512 a backplane. Theinput circuits 2550 can also be configured to receive data packets fromthe system data lane 2512 c, as well as provide data packets to thesystem data lane 2512 c when commanded. In some embodiments, the inputcircuits can provide various coupling interfaces for different sensorssupported by the monitoring system.

FIG. 30 shows a magnified view of the input circuits 2550. As shown inthe illustrated example, the input circuits 2550 can include a circuitcontroller 2520 a and a node 2522 a configured to facilitate and controlelectronic communication between the circuit controller and thebackplane. The circuit controller 2520 a can generally be similar to thecircuit controller 320. The circuit controller 2520 a can be configuredto receive analog sensor signals from the sensors and convert the analogsensor signals to digital signals at a fixed rate. The circuitcontroller 2520 a can also be configured to normalize the digitalsignals and provide the normalized digital signals to a correspondinginput data lane on the backplane (e.g., via the node 2522 a). In someembodiments, the circuit controller 2520 can be configured to filter theanalog sensor signals to provide aliasing protection for an output rateof the digitized sensor signal. The circuit controllers 2520 a can alsocommunicate with smart sensors (e.g., transducers) to receive asset dataand to issue commands to the transducers. In some embodiments, the inputcircuits can also provide power to the sensors.

Each node 2522 a of the input circuits 2550 can include schedulecontroller 2534, a node controller 2524, a gate controller 2526, a gatepairs 2528, as well as a transmitter 2530. The schedule controller 2534,a node controller 2524, a gate controller 2526, a gate pairs 2528, aswell as a transmitter 2530, can generally be similar to the schedulecontroller 334, node controller 324, gate controllers, 326, gate pairs328, and transmitter 330. The gate pair 2528 can include a transmitterand a receiver. The node controller 2524 can function as an interfacebetween the circuit controller 2520 a and the gate controller 2526,transmitters 330 and/or receivers 332. For example, the node controller2524 can be configured to control which data is transferred from thesystem data lane 2512 c to the circuit controller 2520 a using, e.g.,packet filtering techniques. In some embodiments, the node controller2524 can be configured to receive signals from the circuit controller2520 a, encode the signals into bits, and deliver signals (e.g., datapackets) corresponding to the encoded bits to the gate controller 2526for the data to be delivered to the input data lane 2512 a of thebackplane 2506.

In some embodiments, the schedule controller 2534 can be configuredmanage timing of communication from the input circuits 2550 to the inputdata lanes 2512 a and/or the serial data lanes. For example, in someembodiments, data packets can be delivered to input data lanes 2512 ausing time division multiplexing. The schedule controllers 2534 cangenerate schedules and/or algorithms that can be managed by the nodecontrollers 2524 and/or gate controllers 2526 to enable successfuldeliver of data packets. The schedules can generally be similar to theschedules described above with regard to FIGS. 4, 7-9 . Utilizing timedivision multiplexing can allow multiple input circuits 2550 to deliverdata to a single input data 2512 a lane while eliminating, ormitigating, collisions between data packets.

The gate pair 2528 can be configured to facilitate electroniccommunication between the input circuit 2550 and the system data lanes2512 c of the backplane 306. In some embodiments, the gate pair 2528 canbe a half-duplex transceiver or a full-duplex transceiver. Each gatecontroller 2526 can be configured to control operation of thetransmitter 2530 as well as a transmitter and receiver of the gate pair2528.

FIG. 31 shows a magnified view of the system interface circuit 2554. Thesystem interface circuit 2554 can be in electronic communication withone of the input data lanes 2512 a, as well as with the system data lane2512 c. The system interface circuit 2554 can be configured to enableadjustment of operating parameters of functional circuits coupled to thebackplane. As shown in the illustrated example, the system interfacecircuit 2554 can include a circuit controller 2520 b and a node 2522 bconfigured to enable and control electronic communication between thecircuit controller 2520 b and the system data lane 2512 c of thebackplane. Circuit controllers 2520 b of system interface circuits canfunction to enable configuration of any of the functional circuits,alarm conditions for protection of the industrial equipment, andconditions for actuation of relay circuits 2558. In some embodiments,the circuit controller 2520 b of the system interface circuit 2554 canbe coupled to the control system and/or a HMI (e.g., HMI 220). A trusteduser, such as, e.g., a plant operator, can provide configuration data tothe circuit controller 2520 b of the system interface circuit 2554 viathe control system and/or the HMI, and the system interface circuit 2554can provide data packets characterizing the configuration data to thesystem data lane 2512 c of the backplane 2506.

The node 2522 b of the system interface circuit 2554 can includeschedule controller 2534, a node controller 2524, a gate controller2526, and a gate pair 2528. The schedule controller 2534, nodecontroller 2524, gate controller 2526, gate pairs 2528, and transmitters2530, can generally be similar to the schedule controller 334, nodecontroller 324, gate controllers, 326, gate pairs 328. The gate pair2528 can include a transmitter and a receiver. In some embodiments, thegate pair 2528 can be a half-duplex transceiver or a full-duplextransceiver. The node controller 2524 can function as an interfacebetween the circuit controller 2520 b and the gate controller 2526and/or the gate pair 2528. In some embodiments, the node controller 2525be configured to receive signals from the circuit controller 2520 b,encode the signals into bits, and deliver signals (e.g., data packets)corresponding to the encoded bits to the gate controller 2526 for thedata to be delivered to the system data lane 2512 c of the backplane2506.

The gate pair 2528 can be configured to facilitate electroniccommunication between the system interface circuit and the system datalanes 2512 c of the backplane. Each gate controller 2526 can beconfigured to control operation of the transmitter as well as thetransmitter and receiver of the gate pair 2528.

In some embodiments, the system interface circuit 2554 can be in amaster/slave relationship with other monitoring circuits 2510 that arein electronic communication with the system data lane 2512 c. Therefore,the system interface circuit 2554 can deliver commands to the inputcircuits 2550, protection circuits 2552, relay circuit 2558, gatewaycircuit 2559, and 4-20 output circuit 2561, thereby commanding responsesfrom the input circuits 2550, protection circuits 2552, relay circuit2558, gateway circuit 2559, and 4-20 output circuit 2561. The inputcircuits 2550, protection circuits 2552, relay circuit 2558, gatewaycircuit 2559, and 4-20 output circuit 2561 can receive the command, anddeliver data to the system data lane 2512 c based on the response. Asanother example, in some embodiments, if the input data lanes 2512 aand/or protection data lanes 2512 b are configured to each receive datafrom more than one input circuit 2550 and protection circuit 2552,respectively, the schedule controller 2534 can be configured to generatea communication schedule that determines when each of the input circuit2550 and/or protection circuits 2552 can deliver data to the system datalane 2512 c. The schedules can generally be similar to the schedulesdescribed above with regard to FIGS. 4, 7-9 . The schedule controller2534 can generate a schedule and deliver the schedule to the system datalane 2512 c via the node controller 2524 and/or the gate controller2526. Monitoring circuits 2510 that are in electronic communication withthe system data lane 2512 c can receive the schedule, and deliver datapackets to the system data lane 2512 c based on time slices that theyhave been assigned.

In some embodiments, if multiple monitoring circuits communicate over asingle data lane (e.g., using time division multiplexing), the systeminterface circuit 2554 can be configured to monitor the all of the datalanes.

FIG. 32 shows a magnified view of the protection circuits 2552. Theprotection circuits can be configured to monitor sensor data provided tothe input data lanes 2512 a. The protection monitoring system can alsobe configured to determine a status (e.g., OK, alert, danger, etc.) ofthe industrial equipment that is being monitored based on the sensordata. As shown in the illustrated example, the protection circuit 2552can include a circuit controller 2520 c and a node 2522 c configured tofacilitate and control electronic communication between the circuitcontroller 2520 c and the system data lane 2512 c, a protection datalane, and the input data lanes 2512 a of the backplane 2506.

The circuit controller 2520 c can be configured to retrieve any datapackets (e.g., data packets corresponding to sensor measurements) fromthe input data lanes 2512 a of the backplane 2506 (e.g., via the node2522 c), analyze the retrieved data packets, and provide the results ofsuch analysis to one of the protection data lanes 2512 b of thebackplane 2506 (e.g., via the node 2522 c). For example, circuitcontrollers 2520 c of protection circuits 2552 can also be configured tocompare data received from the backplane 2506 to pre-determined alarmconditions in real-time and determine a status (e.g., OK, alert, danger,etc.) for any measured operational parameter or variable, alone or incombination. The determined status can be subsequently output to one ormore of the protection data lanes 2512 b of the backplane 2506. Theprotection circuits 2552 can also be configured to receive data packetsfrom the system data lane 2512 c, as well as provide data packets to thesystem data lane 2512 c, when commanded (e.g., when scheduled tocommunicate).

Each node 2522 c of the protection circuit can include schedulecontroller 2534, a node controller 2524, a gate controller 2526, and agate pair 2528, a transmitter 2530, and receivers 2532. The schedulecontroller 2534, node controllers 2524, gate controllers 2526, gate pair2528, transmitters 2530, and receivers 2532 can generally be similar tothe schedule controller 334, node controller 324, gate controllers 326,gate pairs 328, transmitters 330, and receivers 332. The gate pair 2532can include a transmitter and a receiver. In some embodiments, the gatepair 2528 can be a half-duplex transceiver or a full-duplex transceiver.The node controller 2524 can function as an interface between thecircuit controller 2520 c and the gate controller 2526 and/or gates andthe gate pair. For example, the node controller 2524 can be configuredto control which data is transferred from the input data lanes 2512 a tothe circuit controller 2520 c using, e.g., packet filtering techniques.In some embodiments, the node controller 2524 can be configured toreceive signals from the circuit controller 2520 c, encode the signalsinto bits, and deliver signals (e.g., data packets) corresponding to theencoded bits to the gate controller 2526 for the data to be delivered tothe system data lane 2512 c of the backplane 2506.

The gate pairs 2528 can be configured to facilitate electroniccommunication between the protection circuit 2552 and the system datalane 2512 c. The receivers 2532 can be configured to facilitatecommunication between the protection circuits 2552 and the input datalanes 2512 a. The transmitter 2530 can be configured to facilitatedeliver of data packets (e.g., corresponding to alarms) to one or moreof the protection data lanes 2512 b. Each gate controller 2526 can beconfigured to control operation of the transmitter 2530, the receivers2532, and the gate pair 2528.

As shown in FIGS. 29, 30, and 32 , each input circuit 2550 is configuredto deliver data to a different input data lane 2512 a, and eachprotection circuit 2552 is configured to deliver data to a differentprotection data lane 2512 b. Therefore, each of the input data lanes2512 a and protection data lanes 2512 b is dedicated to a single inputcircuit 2550 and protection circuit 2552, respectively.

FIG. 33 shows a magnified view of the relay circuit 2558. The relaycircuit 2558 can be configured to receive status data (e.g., dataprovided by the protection circuits) from the protection data lanes 2512b and deliver a signal to trusted system (e.g., customer control system212) to alert plant operators of potential problems related to operationof industrial systems, and or trigger a shutdown of the industrialsystem. In some embodiments, the one or more of the relay circuit 2558can be a protection fault relay and will also have provide an alert, orindication, when the user has placed the system in a mode of operationthat compromises protection.

As shown in the illustrated example, the relay circuit 2558 can includea circuit controller 2520 d and node 2522 d configured to facilitate andcontrol electronic communication between the circuit controller 2520 dand the system data lane 2512 c as well as each of the protection datalanes 2512 b. The circuit controller 2520 d of the relay circuit 2558can be configured to retrieve status data (e.g., data delivered byprotection circuits) from protection data lanes 2512 b of the backplane2506 (e.g., via the node 2522 d) and to actuate based on the systemstatus. In one example, circuit controllers 2520 d of relay circuit 2558can actuate based upon a single status. In another example, relaycircuit 2558 can actuate based upon Boolean expressions (e.g., AND orvoting) that combine two or more statuses. In some embodiments, uponactuation, relay circuit 2558 can be configured to deliver a monitoringsignal (e.g., monitoring signal 106 s) to a control system (e.g.,customer control system 212). The control system can then stop operationof the equipment being monitored to prevent damage or failure.

Each node 2522 d of the relay circuit 2558 can include schedulecontroller 2534, a node controller 2524, a gate controller 2526, and agate pair, a transmitter 2530, and receivers 2532. The schedulecontroller 2534, node controllers 2524, gate controllers 2526, gate pair2528, transmitters 2530, and receivers 2532 can generally be similar tothe schedule controller 334, node controller 324, gate controllers 326,gate pairs 328, transmitters 330, and receivers 332. In someembodiments, the gate pair 2528 can be a half-duplex transceiver or afull duplex transceiver. The node controller 2524 can function as aninterface between the circuit controller 2520 d and the gate controller2526, transmitter 2530, receivers 2532 and/or the gate pair 2528. Forexample, the node controller 2524 can be configured to control whichdata is transferred from the protection data lanes 2512 b to the circuitcontroller 2520 d using, e.g., packet filtering techniques. In someembodiments, the node controller 2524 can be configured to receivesignals from the circuit controller 2520 d, encode the signals intobits, and deliver signals (e.g., data packets) corresponding to theencoded bits to the gate controller 2526 for the data to be delivered tothe system data lane 2512 c of the backplane 2506.

FIG. 34 shows a magnified view of the gateway circuit 2559. As shown inthe illustrated example, the gateway circuit 2559 can include a circuitcontroller 2520 e and a node 2522 e configured to enable and controlelectronic communication between the circuit controller 2520 e and thesystem data lane 2512 c as well as each of the protection data lanes2512 b. The gateway circuit 2559 can enable communication between theflexible monitoring system 202 and trusted system such as, e.g., the HMI220, customer historian 216, and customer control systems 212. Forexample, the protection circuits 2552 can deliver data characterizingoperation of a machine (e.g., machine 102) to the gateway circuit 2559.The gateway circuit 2559 can provide the data to a trusted user and/orsystem (e.g., HMI 220, customer historian 216, and customer controlsystems 212). In some embodiments, the gateway circuit 2559 can alsofunctions as input circuit. For example, a trusted user and/or systemsuch as, e.g., the HMI 220, customer historian 216, and customer controlsystems 212, can provide data to the gateway circuit, and the gatewaycircuit 2559 can deliver the data to the backplane 2506 such that thedata is available to other functional circuits. For example, a trusteduser can deliver data to the gateway circuit 2559 to request that theprotection circuit 2552 perform certain analyses on sensor data. In someembodiments, if the gateway circuit 2559 can include a transmitter suchthat the gateway circuit can receive the request and deliver the datacharacterizing the request to the backplane 2506.

Each node 2522 e of the gateway circuit 2559 can include schedulecontroller 2534, a node controller 2524, a gate controller 2526, and agate pair 2528, and receivers 2532. The schedule controller 2534, nodecontrollers 2524, gate controllers 2526, gate pair 2528, transmitters2530, and receivers 2532 can generally be similar to the schedulecontroller 334, node controller 324, gate controllers 326, gate pairs328, transmitters 2530, and receivers 2532. The gate pair 2528 caninclude a transmitter and a receiver. In some embodiments, the gate paircan be a half-duplex transceiver or a full-duplex transceiver. The nodecontroller 2524 can function as an interface between the circuitcontroller 2520 e and the gate controller 2526, receivers 2532, and/orthe gate pair 2528. For example, the node controller 2524 can beconfigured to control which data is transferred from the protection datalanes 2512 b to the circuit controller 2520 e using, e.g., packetfiltering techniques. In some embodiments, the node controller 2524 canbe configured to receive signals from the circuit controller 2520 e,encode the signals into bits, and deliver signals (e.g., data packets)corresponding to the encoded bits to the gate controller 2526 for thedata to be delivered to the system data lane 2512 c of the backplane2506.

FIG. 35 shows a magnified view of the condition monitoring circuit 2556and the 4-20 output circuit 2561, both of which can be configured tooutput 4-20 mA record outputs. The condition monitoring circuit 2556 andthe 4-20 output circuit 2561 can be configured to output monitoringsignals as 4-20 mA recorder outputs. The condition monitoring circuit2556 can be configured to receive all data delivered to the input datalanes 2512 a, protection data lanes 2512 b, and system data lane 2512 c.

As shown in the illustrated example, the condition monitoring circuit2556 can include a circuit controller 2520 f and a node 2522 fconfigured to enable and control electronic communication between thecircuit controller 2520 f and the system data lane 2512 c as well aseach of the input data lanes 2512 a. The node 2522 f of the conditionmonitoring circuit 2556 can include a node controller 2524, a gatecontroller 2526, and receivers 2532. However the node 2522 f of thecondition monitoring circuit 2556 does not include transmitters. Due tothe lack of transmitters, nodes 2522 of 4-20 functional circuit 2556 canis unable to deliver data to the input data lanes 2512 a, protectiondata lanes 2512 b, and the system data lane 2512 c.

The 4-20 output circuit 2561 can be configured to receive all datadelivered to the protection data lanes 2512 b and the system data lane2512 c. As shown in the illustrated example, the 4-20 output circuit2561 can include a circuit controller 2520 g and a node 2522 gconfigured to enable and control electronic communication between thecircuit controller 2520 g and the system data lane 2512 c as well aseach of the protection data lanes 2512 b. The node 2522 g of the 4-20output circuit 2561 can include a node controller 2524, a gatecontroller 2526, and receivers 2532. The node controllers 2524, gatecontrollers 2526, and receiver 2532 can generally be similar to the nodecontroller 324, gate controllers 326, and receivers 332.

As shown in FIGS. 29-34 , transmitters 2530 of each of the inputcircuits 2550 is electrically coupled to a different input data lane2512 a. Therefore, each of the input circuits 2550 delivers data packetsto a different input data lane 2512 a than the other input circuits2550. Similarly, transmitters 2530 of protection circuits 2552 areelectrically coupled to different protection data lanes 2512 b.Therefore, each of the protection circuits 2552 delivers data packets toa different protection data lane 2512 b than the other input circuits2550. By coupling different input data lanes 2512 a and protection datalanes 2512 b to each input circuit 2550 and protection circuit 2552respectively, there is no risk of collisions when delivering data to thebackplane 2506. Since the input data lanes 2512 a and protection datalanes 2512 b do not receive inputs from multiple input circuits 2550 andprotection circuits 2552, respectively, a communication protocolgoverning data delivery to the backplane 2506 can be simplified. Forexample, in some embodiments, there is no need to schedule communicationfrom input circuits 2550 and protection circuits 2552.

In some embodiments, the data lanes that receive data packets from inputcircuit 2550 and protection circuit 2552 can be determined by the ports2508 of the backplane 2506. FIG. 36 shows a top view of the backplane2506 of the monitoring system 2500. As shown in the illustrated example,each port includes first and second input links 2562, 2564. Each ofinput links 2562 can be in electronic communication with a differentinput data lane 2512 a than the other input links 2562. Each port canalso include first and second sets of output links 2566, 2568, andsystem links 2570. In FIG. 36 , the first and second sets of outputlinks 2566, 2568 are illustrated along the input data lanes 2512 a andthe protection data lanes 2512 b, respectively. Each of the output links2566, 2568 can be in electronic communication with a corresponding inputdata lane 2512 a and protection data lane 2512 b, respectively.Therefore, all functional circuits 2510 coupled to the ports 2508 canreceive data from all of the data lanes 2512 a, 2518 b, 2512 c. Thesystem links 2570 can be in electronic communication with the systemdata lane 2512 c and can be configured to facilitate bi-directionalserial communication with the system data lane 2512 c.

Referring to FIGS. 29-36 , in the illustrated example, the inputcircuits are 2512 coupled to ports 2508 a, the protection circuits 2552are coupled to ports 2508 b, the relay circuit 2558, the gateway circuit2559, and the 4-20 output circuit are coupled to ports 2508 c, thecondition monitoring circuit 2556 is coupled to port 2508 d, and thesystem interface circuit is coupled to port 2508 e. However, since eachport 2508 includes input links 2562, 2564, output links 2566, 2568, andsystem links 2570, functional circuits 2510 can be coupled to any givenport 2508 of the backplane 2506. In FIGS. 29-36 transmitters 2530 of theinput circuits 2550 can be electrically coupled to input links 2562 ofthe ports 2508 a, and transmitters 2530 of the protection circuits 2552can be electrically coupled to the input links 2564 of the ports 2508 b.

FIG. 37 shows a data flow diagram 2600 illustrating exemplarycommunication between various components of the monitoring system 2500.At step 2602, the input circuits can deliver data packets characterizingsensor measurements to respective input data lanes 2512 a (e.g., via thefirst input links 2562 of the ports 2508 a). At step 2604, theprotection circuits 2552 can receive the data packets from the inputdata lanes 2512 a. At step 2606, the condition monitoring circuit 2556can receive the data packets from the input data lanes 2512 a.

The protection circuits 2552 can analyze and process the data from theinput data lanes. For example, the protection circuits 2552 candetermine an operating status of a machine based on the sensormeasurements. At step 2608, the protection circuits 2552 can provide theresults of such analyses to the protection data lanes 2512 b (e.g., viathe second input links 2564 of the ports 2508 b). At steps 2610, 2612,2614, 2616, 2618, the relay circuit 2558, gateway circuit 2559, 4-20output circuit 2561, and condition monitoring circuit 2556 can receivethe data from the protection data lanes 2512 b, respectively.

Based on the status of the machine, the relay circuit 2558 can deliver asignal to a control system (e.g., customer control system 212). Thecontrol system can then stop operation of the equipment being monitoredto prevent damage or failure. In some embodiments, the conditionmonitoring circuit 2556 can perform further analysis on data receivedfrom the input data lanes 2512 a and the protection data lanes 2512 b.The condition monitoring circuit 2556 can provide data from the inputdata lanes 2512 a and the protected data lanes 2512 b to untrusted usersor systems (e.g., remote technical support operators and conditionmonitoring system 214). The gateway circuit 2559 can provide data fromthe protection data lanes 2512 b to trusted system such as, e.g., theHMI 220, customer historian 216, and customer control systems 212. The4-20 output circuit can provide from the protection data lanes 2512 b toa trusted user (e.g., a plant operator). During operation, the systeminterface circuit 2554 can deliver data packets to the system data lane2512 c to adjust operating parameters of functional circuits 2510coupled to the backplane and/or request status updates from each of theother functional circuits 2510 coupled to the backplane 2506. A trusteduser, such as, e.g., a plant operator, can provide configuration data tothe circuit controller 2520 b of the system interface circuit 2554 viathe control system and/or the HMI, and the system interface circuit 2554can provide data packets characterizing the configuration data to thesystem data lane 2512 c of the backplane 2506. The input circuits 2550,protection circuits 2552, relay circuit 2558, gateway circuit 2559, 4-20output circuit 2561, and the condition monitoring circuit 2556 canreceive the data from the system data lane 2512 c, update operatingparameters based on the received data, and/or provide status responsesto the system data lane 2512 c if requested.

Periodically, each functional circuit 2510 of the monitoring system 2500can perform self-tests to evaluate a status of internal processors,memory, and/or other circuitry. The functional circuit can alsodetermine a current operating status. Each of the functional circuit candeliver the results of the self—test to the system data lane 2512 c tobe provided to the statuses will be sent on the system data lane 2512 cand can be sent over the various data lanes. The system interfacecircuit 2554 can also provide an additional level of analysis at asystem level. Included in the health analysis with telemetry data(system temperature, hours in use, supply voltage), configurationchanges, network performance information. The system interface circuit2554 can deliver data characterizing results of the health analysis tothe system data lane 2512 c such that each functional circuit canreceive the data.

In some embodiments, the monitoring system can be configured to deliverdata to a local displays such that the data can be displayed for a plantoperator. In other embodiments, data can be transmitted using industrialprotocols such that it is available for presentation on HMIs. The datacan include current values, status, and/or trends of measure values.

In some embodiments, the system interface circuit 2554, a gatewaycircuit 2559, and/or a condition monitoring circuit 2556 can include ashort range wireless communication components such that each of thesystem interface circuit 2554, a communication gateway, and/or acondition monitoring circuit 2556 can be configured to communicatewirelessly with a user device. In some embodiments, the system interfacecircuit 2554, a communication gateway, and/or a condition monitoringcircuit can provide health information to a user device such as, e.g., atablet, laptop, smartphone, etc. In some embodiments, the system caninclude a 4-20 mA recorder output.

By utilizing different input data lanes 2512 a and protection data lanes2512 b to receive data from each input circuit 2550 and protectioncircuit 2552 respectively, there is no risk of collisions whendelivering data to the backplane 2506. Since the input data lanes 2512 aand protection data lanes 2512 b do not receive inputs from multipleinput circuits 2550 and protection circuits 2552, respectively, acommunication protocol governing data delivery to the backplane 2506 canbe simplified. For example, in some embodiments, there is no need toschedule communication from input circuits 2550 and protection circuits2552. Additionally, by separating functionality of input data lanes 2512a and protection data lanes 2512 b, circuitry of nodes 2522 of eachfunctional circuit 2510 can be simplified such that it can be designedand constructed more efficiently.

In some embodiments, a backplane of a monitoring systems can includededicated data lanes that are not separated by functionality, but whichare still configured to receive data input from a single monitoringcircuit. FIG. 38 shows block diagram of a portion of another exemplaryembodiment of a monitoring system 2700.

The monitoring system 2700 can include any number of functional circuits2710, which can be detachably coupled to a backplane 2706 via ports 2708of the backplane 2706. As shown in the illustrated example, themonitoring system 2700 includes input circuits 2750, protection circuits2752, a system interface circuit 2754, a relay circuit 2758, a 4-20output circuit 2761, and a condition monitoring circuit 2756. The inputcircuits 2750, protection circuits 2752, a system interface circuit2754, relay circuit 2578, a 4-20 output circuit 2761, and conditionmonitoring circuit 2756 can generally be similar to the protectioncircuits 2552, system interface circuit 2554, relay circuit 2558, 4-20output circuit 2561, and condition monitoring circuit 2556 describeherein with regard to FIGS. 29-36 , with the exception of some slightdifference between nodes of each, as described in more detail below.

In the illustrated example, the backplane includes a set of data lanes2712 a, and at least one system data lane 2712 c. The data lanes 2712 acan serve the same functions as the input data lanes 2512 a and theprotection data lanes 2512 b. The system data lane 2712 c can generallyfunction similarly to the system data lane 2512 c. Each of the inputdata lanes 2712 a can be configured to receive data packets from aninput circuits 2750 coupled to a port 2708 that can be configured tofacilitate data delivery to the corresponding data lane 2712 a. As shownin the illustrated example, each data lane 2712 a can receive datapackets from a single input circuit 2550 or a single protection circuit2752. All of the data lanes 2712 a and system data lanes 2712 c can beelectrically coupled to each of the ports 2708. However, for clarity,unused connections between the ports 2708 and data lanes 2712 a and/orsystem data lanes 2712 c are omitted in FIGS. 38-42 .

The backplane 2706 can be a passive backplane configured to facilitatemultipoint asynchronous electronic communication between the functionalcircuits that are coupled to the backplane. Therefore, all data that isdelivered to the backplane 2706 can be received by all functionalcircuits 2710 that are coupled to the backplane 2706.

FIG. 39 shows a magnified view of the input circuits 2750 and the systeminterface circuit 2754. As shown in the illustrated example, the inputcircuits 2750 can include a circuit controller 2720 a and a node 2722 aconfigured to facilitate and control electronic communication betweenthe circuit controller and the backplane 2706. The circuit controller2720 a can generally be similar to the circuit controller 2520 a. Eachnode 2722 a of the input circuits 2750 can include a schedule controller2534, a node controller 2524, a gate controller 2526, a gate pairs 2528,and a transmitter 2530. Each of the transmitters 2530 of the inputcircuits 2750 can be in electronic communication with one data lane 2712a. The transmitters 2530 can be configured to deliver data to onecorresponding data lane 2712 a. Each gate pair 2528 of the inputcircuits 2750 can be in electronic communication with the system datalane 2712 c.

The system interface circuit 2754 can include a circuit controller 2720b and a node 2722 b configured to facilitate and control electroniccommunication between the circuit controller and the backplane 2706. Thecircuit controller 2720 b can generally be similar to the circuitcontroller 2520 b. The node 2722 b of the system interface circuit 2754can include a schedule controller 2734, a node controller 2724, a gatecontroller 2726, and gate pairs 2728. The gate pair 2528 of the systeminterface circuit 2754 can be in electronic communication with thesystem data lane 2712 c.

FIG. 40 shows a magnified view of the protection circuits 2752. As shownin the illustrated example, the protection circuits 2752 can include acircuit controller 2720 c and a node 2722 c configured to facilitate andcontrol electronic communication between the circuit controller 2720 cand the backplane 2706. The circuit controller 2720 c can generally besimilar to the circuit controller 2520 c. Each node 2722 c of theprotection circuits 2752 can include a schedule controller 2534, a nodecontroller 2524, a gate controller 2526, a gate pairs 2528, atransmitter 2530, and receivers 2532. Each of the transmitters 2530 ofthe protection circuits 2752 can be in electronic communication with onedata lane 2712 a. The transmitters 2530 can be configured to deliverdata to one corresponding data lane 2712 a. Each gate pair 2528 of theinput circuits 2750 can be in electronic communication with the systemdata lane 2712 c. The receivers 2532 can be in electronic communicationwith the data lanes 2712 a, and can be configured to receive data fromthe data lanes 2712 a. The protection circuits 2752 can include asufficient number of receivers 2532 to be able to receive data from allof the data lanes 2712 a.

FIG. 41 shows a magnified view of the relay circuit 2758, 4-20 outputcircuit 2761, and a condition monitoring circuit 2756. The relay circuit2758, 4-20 output circuit 2761, and a condition monitoring circuit 2756can include circuit controllers 2720 d, 2720 g, 2720 f, and nodes 2722d, 2722 g, 2722 f. The nodes 2722 d, 2722 g, 2722 f can be configured tofacilitate and control electronic communication between the circuitcontrollers 2720 d, 2720 g, 2720 f and the backplane 2706. The circuitcontrollers 2720 d, 2720 g, 2720 f can generally be similar to thecircuit controllers 2520 d, 2520 g, 2520 f. Each of the nodes 2722 d,2722 g, 2722 f can include a schedule controller 2534, a node controller2524, a gate controller 2526, a gate pairs 2528, and receivers 2532. Thegate pairs 2528 of the relay circuit 2758, 4-20 output circuit 2761, anda condition monitoring circuit 2756 can be in electronic communicationwith the system data lane 2712 c. The receivers 2532 can be inelectronic communication with the data lanes 2712 a, and can beconfigured to receive data from the data lanes 2712 a. The relay circuit2758, 4-20 output circuit 2761, and a condition monitoring circuit 2756can each include a sufficient number of receivers 2532 to be able toreceive data from all of the data lanes 2712 a.

In some embodiments, the data lanes 2712 a that receive data packetsfrom input circuit 2750 and protection circuit 2752 can be determined bythe ports 2708 of the backplane 2706. FIG. 42 shows a top view of thebackplane 2706 of the monitoring system 2700. As shown in theillustrated example, each port 2706 includes an input link 2762. Each ofinput links 2762 can be in electronic communication with a differentdata lane 2712 a than the other input links 2762.

Each port 2706 can also include a sets of output links 2766, and systemlinks 2570. In FIG. 42 , the output links 2766 are illustrated along thedata lanes 2712 a. Each of the output links 2766 can be in electroniccommunication with a corresponding data lane 2712 a. Therefore, allfunctional circuits 2710 coupled to the ports 2708 can receive data fromall of the data lanes 2712 a. The system links 2770 can be in electroniccommunication with the system data lane 2712 c and can be configured tofacilitate bi-directional serial communication with the system data lane2512 c.

Referring to FIGS. 38-42 , in the illustrated example, the inputcircuits 2750 are coupled to ports 2708 a, the protection circuits 2752are coupled to ports 2708 b, relay circuit 2758, 4-20 output circuit2761, and a condition monitoring circuit 2756 are coupled to ports 2708c, and the system interface circuit is coupled to port 2708 e. However,since each port 2708 includes input links 2762, output links 2766, andsystem links 2770, functional circuits 2710 can be coupled to any givenport 2708 of the backplane 2706. In FIGS. 38-42 , transmitters 2730 ofthe input circuits 2750 and protection circuits 2752 can be electricallycoupled to input links 2762 of the ports 2708 a, 2708 b. Any receiversof the functional circuits 2710 can be coupled to the output links 2766.

Traditional monitoring systems can be limited in terms of flexibilityand scalability. Additionally, costs and complexity of installation cancreate a significant barrier to entry for users that want to monitor lowcost and/or low priority components/systems. By utilizing functionalcircuits that can be detachably coupled to the backplane, performance ofthe monitoring systems described herein can be adjusted and/or scaled tofit individual monitoring needs. For example, processing power can beincreased by coupling additional processing circuits to the backplane.As another example, the monitoring system can be expanded by couplingadditional input circuits to the backplane to such that the monitoringsystem can to receive and process sensor data from additional sensors.

Exemplary technical effects of the subject matter described herein caninclude the ability to customize and adjust capabilities of a monitoringsystem through selection and application of various different types offunctional circuits, as described here. Another exemplary technicaleffect includes the ability to share all data delivered to a backplaneof a monitoring system, thereby allowing for resources (e.g., functionalcircuits) to be distributed between the backplanes as desired. Forexample, monitoring subsystems can be installed remotely near industrialequipment such that the input circuits can receive sensor data, whileother monitoring subsystems can be installed at another location thatmay be more convenient, or easier to access. Installing monitoringsubsystems near the industrial equipment to be monitored can also reducecosts of running cables from the sensors to input circuits, as well asimprove the quality of the signals delivered from sensors to the inputcircuits by reducing exposure to noise and ground loops. Additionally,utilizing backplanes that have dedicated data lanes can minimizedisruption associated with hardware failure while maintainingflexibility and scalability of the monitoring system.

One skilled in the art will appreciate further features and advantagesof the subject matter described herein based on the above-describedembodiments. Accordingly, the present application is not to be limitedspecifically by what has been particularly shown and described. Allpublications and references cited herein are expressly incorporatedherein by reference in their entirety.

Other embodiments are within the scope and spirit of the disclosedsubject matter. Those skilled in the art will understand that thesystems, devices, and methods specifically described herein andillustrated in the accompanying drawings are non-limiting exemplaryembodiments and that the scope of the present invention is definedsolely by the claims. The features illustrated or described inconnection with one exemplary embodiment may be combined with thefeatures of other embodiments. Such modifications and variations areintended to be included within the scope of the present invention.

Further, in the present disclosure, like-named components of theembodiments generally have similar features, and thus within aparticular embodiment each feature of each like-named component is notnecessarily fully elaborated upon. Additionally, to the extent thatlinear or circular dimensions are used in the description of thedisclosed systems, devices, and methods, such dimensions are notintended to limit the types of shapes that can be used in conjunctionwith such systems, devices, and methods. A person skilled in the artwill recognize that an equivalent to such linear and circular dimensionscan easily be determined for any geometric shape

In the descriptions above and in the claims, phrases such as “at leastone of” or “one or more of” may occur followed by a conjunctive list ofelements or features. The term “and/or” may also occur in a list of twoor more elements or features. Unless otherwise implicitly or explicitlycontradicted by the context in which it is used, such a phrase isintended to mean any of the listed elements or features individually orany of the recited elements or features in combination with any of theother recited elements or features. For example, the phrases “at leastone of A and B;” “one or more of A and B;” and “A and/or B” are eachintended to mean “A alone, B alone, or A and B together.” A similarinterpretation is also intended for lists including three or more items.For example, the phrases “at least one of A, B, and C;” “one or more ofA, B, and C;” and “A, B, and/or C” are each intended to mean “A alone, Balone, C alone, A and B together, A and C together, B and C together, orA and B and C together.” In addition, use of the term “based on,” aboveand in the claims is intended to mean, “based at least in part on,” suchthat an unrecited feature or element is also permissible.

The subject matter described herein can be implemented in digitalelectronic circuitry, or in computer software, firmware, or hardware,including the structural means disclosed in this specification andstructural equivalents thereof, or in combinations of them. The subjectmatter described herein can be implemented as one or more computerprogram products, such as one or more computer programs tangiblyembodied in an information carrier (e.g., in a machine-readable storagedevice), or embodied in a propagated signal, for execution by, or tocontrol the operation of, data processing apparatus (e.g., aprogrammable processor, a computer, or multiple computers). A computerprogram (also known as a program, software, software application, orcode) can be written in any form of programming language, includingcompiled or interpreted languages, and it can be deployed in any form,including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment. Acomputer program does not necessarily correspond to a file. A programcan be stored in a portion of a file that holds other programs or data,in a single file dedicated to the program in question, or in multiplecoordinated files (e.g., files that store one or more modules,sub-programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

The processes and logic flows described in this specification, includingthe method steps of the subject matter described herein, can beperformed by one or more programmable processors executing one or morecomputer programs to perform functions of the subject matter describedherein by operating on input data and generating output. The processesand logic flows can also be performed by, and apparatus of the subjectmatter described herein can be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processor of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. The essential elements of a computer area processor for executing instructions and one or more memory devicesfor storing instructions and data. Generally, a computer will alsoinclude, or be operatively coupled to receive data from or transfer datato, or both, one or more mass storage devices for storing data, e.g.,magnetic, magneto-optical disks, or optical disks. Information carrierssuitable for embodying computer program instructions and data includeall forms of non-volatile memory, including by way of examplesemiconductor memory devices, (e.g., EPROM, EEPROM, and flash memorydevices); magnetic disks, (e.g., internal hard disks or removabledisks); magneto-optical disks; and optical disks (e.g., CD and DVDdisks). The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, the subject matter describedherein can be implemented on a computer having a display device, e.g., aCRT (cathode ray tube) or LCD (liquid crystal display) monitor, fordisplaying information to the user and a keyboard and a pointing device,(e.g., a mouse or a trackball), by which the user can provide input tothe computer. Other kinds of devices can be used to provide forinteraction with a user as well. For example, feedback provided to theuser can be any form of sensory feedback, (e.g., visual feedback,auditory feedback, or tactile feedback), and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The techniques described herein can be implemented using one or moremodules. As used herein, the term “module” refers to computing software,firmware, hardware, and/or various combinations thereof. At a minimum,however, modules are not to be interpreted as software that is notimplemented on hardware, firmware, or recorded on a non-transitoryprocessor readable recordable storage medium (i.e., modules are notsoftware per se). Indeed “module” is to be interpreted to always includeat least some physical, non-transitory hardware such as a part of aprocessor or computer. Two different modules can share the same physicalhardware (e.g., two different modules can use the same processor andnetwork interface). The modules described herein can be combined,integrated, separated, and/or duplicated to support variousapplications. Also, a function described herein as being performed at aparticular module can be performed at one or more other modules and/orby one or more other devices instead of or in addition to the functionperformed at the particular module. Further, the modules can beimplemented across multiple devices and/or other components local orremote to one another. Additionally, the modules can be moved from onedevice and added to another device, and/or can be included in bothdevices.

The subject matter described herein can be implemented in a computingsystem that includes a back-end component (e.g., a data server), amiddleware component (e.g., an application server), or a front-endcomponent (e.g., a client computer having a graphical user interface ora web browser through which a user can interact with an implementationof the subject matter described herein), or any combination of suchback-end, middleware, and front-end components. The components of thesystem can be interconnected by any form or medium of digital datacommunication, e.g., a communication network. Examples of communicationnetworks include a local area network (“LAN”) and a wide area network(“WAN”), e.g., the Internet.

Approximating language, as used herein throughout the specification andclaims, may be applied to modify any quantitative representation thatcould permissibly vary without resulting in a change in the basicfunction to which it is related. Accordingly, a value modified by a termor terms, such as “about” and “substantially,” are not to be limited tothe precise value specified. In at least some instances, theapproximating language may correspond to the precision of an instrumentfor measuring the value. Here and throughout the specification andclaims, range limitations may be combined and/or interchanged, suchranges are identified and include all the sub-ranges contained thereinunless context or language indicates otherwise.

What is claimed is:
 1. A monitoring system, comprising: a firstbackplane having, a first set of data lanes, and a first set of ports,each port of the first set of ports being in electronic communicationwith at least one data lane of the first set of data lanes; a secondbackplane having, a second set of data lanes, and a second set of ports,each of the second set of ports being in electronic communication withat least one data lane of the second set of data lanes; and a firstbridge circuit detachably coupled to at least one of the first set ofports, and a second bridge circuit detachably coupled to at least one ofthe second set of ports; wherein the second bridge circuit is inelectronic communication with the first bridge circuit; wherein thefirst bridge circuit is configured to receive a first set of data fromthe first set of data lanes, convert the first set of data to a firstserial data stream, and to deliver the first serial data stream to thesecond bridge circuit, thereby delivering the first set of data to thesecond backplane; and wherein the second bridge circuit is configured toreceive a second set of data from the second set of data lanes, convertthe second set of data to a second serial data stream, and to deliverthe second serial data stream to the first bridge circuit, therebydelivering the second set of data to the first backplane.
 2. Themonitoring system of claim 1, wherein the first bridge circuitcomprises: at least one first gate configured to facilitate electroniccommunication between the first bridge circuit and at least one datalane of the first set of data lanes, the at least one first gate beingconfigured to operate in a first operating mode and in a secondoperating mode, wherein, the at least one first gate is configured toallow data to be transferred from the first bridge circuit to the atleast one data lane of the first set of data lanes when in the firstoperating mode; and wherein, the at least one first gate is configuredto prevent data from being transferred from the first bridge circuit tothe at least one data lane of the first set of data lanes when in thesecond operating mode; and at least one first gate controller inelectronic communication with the at least one first gate, the at leastone first gate controller being configured control operation of the atleast one first gate.
 3. The monitoring system of claim 2, wherein thesecond bridge circuit comprises: at least one second gate configured tofacilitate electronic communication between the second bridge circuitand at least one data lane of the second set of data lanes, the at leastone second gate being configured to operate in a third operating modeand a fourth operating mode, wherein, the at least one second gate isconfigured to allow data to be transferred from the second bridgecircuit to the at least one lane of the second set of data lanes when inthe third operating mode, and wherein, the at least one second gate isconfigured to prevent data from being transferred from the second bridgecircuit to the at least one lane of the second set of data lanes when inthe fourth operating mode; and at least one second gate controller inelectronic communication with the at least one second gate and the atleast one first gate controller, the at least one second gate controllerbeing configured control operation of the at least one second gate. 4.The monitoring system of claim 1, further comprising: a first set offunctional circuits, each functional circuit of the first set offunctional circuits being detachably coupled to at least one port of thefirst set of ports, the first set of functional circuits beingconfigured to deliver the first set of data to the first backplane andto selectively receive any data delivered to the first backplane; and asecond set of functional circuits, each functional circuit of the secondset of functional circuits being detachably coupled to at least one portof the second set of ports, the second set of functional circuits beingconfigured to deliver a second set of data to the second backplane andto selectively receive any data delivered to the second backplane. 5.The monitoring system of claim 4, wherein the first set of functionalcircuits includes at least one first functional circuit having: at leastone second gate configured to facilitate electronic communicationbetween the at least one first functional circuit and at least one ofthe first set of data lanes, the at least second one gate beingconfigured to operate in a first operating mode and a second operatingmode, wherein, the at least one second gate is configured to allow datato be transferred from the at least one first functional circuit to theat least one lane of the first set of data lanes when in the firstoperating mode, and wherein, the at least one second gate is configuredto prevent data from being transferred from the at least one firstfunctional circuit to the at least one lane of the first set of datalanes when in the second operating mode.
 6. The monitoring system ofclaim 1, wherein the first set of data lanes comprises a plurality ofdata lanes.
 7. The monitoring system of claim 1, wherein the second setof data lanes comprises a plurality of data lanes.
 8. The monitoringsystem of claim 4, further comprising a sensor in electroniccommunication with a functional circuit of at least one of the first setof functional circuits and the second set of functional circuits, thesensor being configured to measure operating parameters of a machine andto deliver data characterizing the measured operating parameters to thefunctional circuit.
 9. The monitoring system of claim 4, wherein thefirst set of functional circuits comprises a plurality of functionalcircuits, each functional circuit of the plurality of functionalcircuits being configured to receive data from at least one data lane ofthe first set of data lanes.
 10. The monitoring system of claim 1,wherein the first backplane and the second backplane are passivebackplanes and do not include active switches.
 11. A method, comprising:receiving a first identification data at a first bridge circuit coupledto a first backplane of a first monitoring subsystem, the firstidentification data characterizing information identifying hardware of asecond monitoring subsystem; receiving a second identification data at asecond bridge circuit coupled to a second backplane of the secondmonitoring subsystem, the second identification data characterizinginformation identifying hardware of the first monitoring subsystem;determining, using the first identification data and the secondidentification data, that first monitoring subsystem is compatible withthe second monitoring subsystem; receiving a first schedule at thesecond bridge circuit, the first schedule characterizing a firstcommunication schedule for a first set of functional circuits that arein electronic communication with the first backplane; receiving a secondschedule at the first bridge circuit, the second schedule characterizinga second communication schedule for a second set of functional circuitsthat are in electronic communication with the second backplane;comparing the first communication schedule to the second communicationschedule; determining that the first schedule is compatible with thesecond schedule; and providing a first signal to at least one first gateof the first bridge circuit and providing a second signal to at leastone second gate of the second bridge circuit, thereby activating the atleast one first gate and the at least one second gate, and facilitatingelectronic communication between the first backplane and the secondbackplane.
 12. The method of claim 11, further comprising: delivering,from the first set of functional circuits, a first set of parallel datastreams to a first set of parallel data lanes of the first backplane;receiving, at the first bridge circuit, the first set of parallel datastreams from the first set of parallel data lanes of the firstbackplane; converting the first set of parallel data streams to a firstserial data stream; delivering the first serial data stream to thesecond bridge circuit; expanding the first serial data stream to asecond set of parallel data streams; and delivering the second set ofparallel data streams to a second set of parallel data lanes.
 13. Themethod of claim 12, further comprising amplifying a power of the firstserial data stream based on a distance between the first bridge circuitand the second bridge circuit.
 14. The method of claim 12, furthercomprising delivering, from the second set of functional circuits, athird set of parallel data streams to the second set of parallel datalanes of the second backplane.
 15. The method of claim 14, furthercomprising: receiving, at the second bridge circuit, the third set ofparallel data streams from the second set of parallel data lanes of thesecond backplane; converting the third set of parallel data streams to asecond serial data stream; delivering the second serial data stream tothe first bridge circuit; expanding the second serial data stream to afourth set of parallel data streams; and delivering the fourth set ofparallel data streams to the first set of parallel data lanes.
 16. Themethod of claim 14, further comprising generating a third schedule usingat least one functional circuit of the first set of functional circuits,the third schedule including data that determines when each functionalcircuit of the first set of functional circuits delivers data to thefirst set of parallel data lanes and when each functional circuit thesecond set of functional circuits delivers data to the second set ofparallel data lanes.
 17. The method of 14, wherein the third set ofparallel data streams includes sensor data characterizing measuredoperating values of a machine, the sensor data being measured by sensorscoupled to the machine.
 18. The method of claim 14, further comprisingamplifying a power of the second serial data stream based on a distancebetween the first bridge circuit and the second bridge circuit.
 19. Themethod of claim 11, further comprising: determining an estimated delaytime characterizing an estimated amount of time required to transferdata between the first bridge circuit and the second bridge circuit;determining a dead band period based on at least one of the firstcommunication schedule and the second communication schedule, the deadband time characterizing a total amount of time available to absorbdelays in communication between one or more backplane; determining anamount of the dead band time that is available based on at least one ofthe first communication schedule and the second communication schedule;and comparing the estimated delay time to the amount of dead band timethat is available.
 20. The method of claim 11, further comprising:receiving a first network identification data at the first bridgecircuit, the first network identification data characterizing a firstnetwork configuration; receiving a second network identification data atthe second bridge circuit, the second network identification datacharacterizing a second network configuration; and comparing the firstnetwork identification data with the second network identification data.